Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add clearsmog/claude-skills --skill context-statusgit clone --depth 1 https://github.com/clearsmog/claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/clearsmog/claude-skills/context-status)<a href="https://agentmods.dev/skills/clearsmog/claude-skills/context-status"><img src="https://agentmods.dev/badge/skills/clearsmog/claude-skills/context-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/clearsmog/claude-skills/context-status"><img src="https://agentmods.dev/badge/skills/clearsmog/claude-skills/context-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.00441 |
| Opus 5.5 | $0.00015 | $0.00176 |
| Sonnet 5.5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
context-status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 24d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
89% identical to context-status — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/context-status — Check Session Health
Show the current session status including context usage estimate, active plan, and preservation state.
What This Skill Shows
- Context usage estimate — Approximate % of context window used
- Active plan — Current plan file and status
- Session log — Most recent session log
- Preservation state — What will survive compaction
Workflow
Step 1: Context usage
There is no on-disk estimate. Claude Code's built-in /context shows actual usage; tell the user to run it for the number.
Step 2: Find Active Plan
Search common plan locations:
ls -lt quality_reports/plans/*.md .planning/*.md plans/*.md 2>/dev/null | head -3
Step 3: Find Session Log
ls -lt quality_reports/session_logs/*.md .planning/logs/*.md session_logs/*.md 2>/dev/null | head -1
Step 4: Report Status
Format the output:
Session Status
-----------------------------------
Context Usage: ~XX% (estimated)
Auto-compact: [approaching | not imminent]
Active Plan
File: [plan path]
Status: [draft | approved | in_progress | completed]
Task: [current unchecked task or "none"]
Session Log
File: [log path]
Preservation Check
- Pre-compact hook: [configured | missing]
- Post-compact restore: [configured | missing]
- Session state will be saved before compaction
Notes
- Context usage comes from
/context - Actual compaction is triggered by Claude Code automatically
- All important state is saved to disk (plans, logs, MEMORY.md)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 24d ago Changed · -4 lines scan B → A 4e8c9c2ebf2c
- 1mo ago First seen · 76 lines · 37 tokens per session scan B e426551ff0ed
context-status is a skill published in the GitHub repository clearsmog/claude-skills (2 stars, last pushed 24d ago), licensed MIT. It adds 37 tokens to every session and 441 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to context-status, differing in 44 lines, and is treated as a copy.
Other skills, from other repositories
godot-optimization
Use when optimizing Godot games — profiler, draw calls, physics tuning, memory management, and common bottlenecks.
iterate-lessons-log
Creates a structured lessons learned entry for organizational memory. Use after an incident, a completed project, or a significant learning to record knowledge for future teams and initiatives. Distinct from iterate-retrospective, which facilitates the team ceremony; this skill writes the durable lessons entry that…
ai-brain
Give Claude a permanent, searchable long-term memory using an Obsidian vault as the store. At the end of a session, summarize what mattered and save it as a Markdown note in your "AI Brain" vault; at the start of a session (or on demand), read back only the relevant past notes. Local markdown you own — connected via…
ac-knowledge-graph-adaptationio-skrillz
This page used to hold an archived copy of this skill. The archive now lives in the registry's data repository.
ac-memory-manager-adaptationio-skrillz-3
This page used to hold an archived copy of this skill. The archive now lives in the registry's data repository.
agent-assistant-nahisaho-musubi
This page used to hold an archived copy of this skill. The archive now lives in the registry's data repository.