Session Watchdog
Monitor session context levels and proactively save checkpoints before compaction. Use when: (1) session context exceeds 80% capacity, (2) user asks about session status or memory, (3) at the start of each new session to check context, or (4) before long tasks that might push context over threshold.
Install
$ agentstack add skill-berabuddies-semia-session-watchdog ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-berabuddies-semia-session-watchdog) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Session Watchdog
Monitors context levels, warns before compaction, and saves checkpoints to preserve important information.
Context Thresholds
| Level | Tokens | Action | |-------|--------|--------| | Safe | 0-140k | Normal operation | | Warning | 140k-160k | Warn user, save checkpoint | | Critical | 160k-197k | Warn + stop unless urgent | | Full | 197k+ | Compaction imminent |
Check Context
Before each session and periodically during long conversations:
session_statusCheck the contextTokens field from the response.
Checkpoint Protocol
When approaching 80% (160k tokens):
- Save checkpoint to memory file:
- Read current memory/YYYY-MM-DD.md
- Add key context: decisions, pending tasks, important details
- Write back to memory file
- Alert user:
Say: "⚠️ Approaching context limit (~160k tokens). Saving checkpoint to memory before continuing."
- Ask user:
- Continue and accept compaction?
- Summarize and restart fresh?
- Pause until ready?
What to Save
Essential information that must survive compaction:
- Decisions made in this conversation
- Pending tasks not yet completed
- Important context (project state, configurations, preferences)
- Files modified and their paths
- Unresolved issues requiring follow-up
When to Trigger
- At session start
- After every 30k tokens of conversation
- Before initiating large tasks (file edits, multiple operations)
- When user asks "how much context do we have left?"
Memory File Format
# YYYY-MM-DD
## Session Checkpoint (at X% context)
### Decisions
- Decision 1
- Decision 2
### Pending
- [ ] Task 1
- [ ] Task 2
### Important Context
- Project state: ...
- Last file modified: ...
### Unresolved
- Issue needing follow-upSource & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: berabuddies
- Source: berabuddies/Semia
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.