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.00455 |
| Opus 5 | $0.00018 | $0.00228 |
| Sonnet 5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade B, and why
context-status scanned grade B with 1 finding 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/sessions/*/context-monitor-cache.json 2>/dev/null | head -20 This is a copy
89% identical to context-status — 33 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: Check Context Monitor Cache
Read the context monitor cache to get the current estimate:
cat ~/.claude/sessions/*/context-monitor-cache.json 2>/dev/null | head -20
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 % is an estimate based on tool call count
- 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.
- 9d 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 6mo ago), licensed MIT. It adds 37 tokens to every session and 455 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 89% identical to context-status, differing in 33 lines, and is treated as a copy.
Other skills, from other repositories
agent-self-improvement
Use when monitor performance of other skills, identify bottlenecks, suggest improvements, and auto-optimize the skill portfolio. Use when monitoring performance of other skills, identify bottlenecks, suggest improvements, and.
kb
Use when querying and maintaining the knowledge base for project context, decisions, and architecture documentation on session start.
find-skills
Use when automatically discover, evaluate, and activate community skills when local skills don't cover user needs. Includes credibility scoring and safety checks for complete OpenClaw self-sufficiency.
joko-orchestrator
Use when deterministically coordinating autonomous planning and execution across available skills under strict guardrails.
vilona
Use when foundational core infrastructure skill providing system foundation capabilities for the agent ecosystem.
berkahkarya-orchestrator
Use when orchestrate multi-skill workflows by routing tasks to the right agents and coordinating cross-platform operations.