Automatic context monitoring for Claude Code — never get interrupted by mid-task compaction again.
SaferSkills independently audited compaction-advisor (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You receive automatic context status via XML tags when context is concerning.
When you see these tags at the start of a conversation turn:
<context-status>CRITICAL: Only 12k tokens free. Run /compact before any task.</context-status>
<context-status>WARNING: 25k tokens free. Only small tasks safe.</context-status>
<context-status>CAUTION: 40k tokens free. Medium tasks OK, compact before large.</context-status>When context is healthy (50k+ free), you won't see any tag.
During multi-step work, you may see:
<context-checkpoint>
CHECKPOINT RECOMMENDED: Context critically low (18k free) after 12 operations.
Good time to pause and /compact. Summarize progress so far and key context to preserve.
</context-checkpoint>This means you've been working for a while and context is running low.
Just before auto-compaction triggers:
<precompact-warning>
AUTO-COMPACTION IMMINENT
Context window is full. Compaction will happen after this message.
</precompact-warning><context-status> CRITICALImmediately advise:
Context is critically low (12k free). Before we proceed, run:
/compact Focus on [relevant context to preserve]<context-status> WARNINGFor small tasks: proceed with caution For medium+ tasks: recommend compaction first
Context is at 25k free. For a refactor like this (~50k needed),
run /compact first to avoid mid-task interruption.<context-checkpoint>This is mid-task. Pause and offer a checkpoint:
Good checkpoint - I've completed:
• [List what you've done so far]
• [Key decisions made]
• [Files modified]
Context is at 18k. To continue safely, run:
/compact Focus on [key context for remaining work]
After compacting, I'll continue with [next steps].<precompact-warning>This is urgent. Quickly summarize:
Compaction is about to happen. Quick summary of our progress:
• [What we were working on]
• [What's been completed]
• [What remains to do]
After compaction, remind me to [specific next step].Context is healthy. Proceed normally without mentioning it.
| Task | ~Tokens Needed |
|---|---|
| Typo fix | 5k |
| Bug fix | 15k |
| New feature | 30k |
| Refactor | 50k |
| Architecture | 80k+ |
/compact # General
/compact Focus on [specific context] # Preserve specific contextExamples:
/compact Focus on the auth changes and test failures/compact Keep the refactoring progress and file structure decisions~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.