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 msiShariful/claude-token-inspector --skill inspect-contextgit clone --depth 1 https://github.com/msiShariful/claude-token-inspectorWrote 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/msishariful/claude-token-inspector/inspect-context)<a href="https://agentmods.dev/skills/msishariful/claude-token-inspector/inspect-context"><img src="https://agentmods.dev/badge/skills/msishariful/claude-token-inspector/inspect-context.svg" alt="Measured on agentmods" 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.00039 | $0.00487 |
| Opus 5 | $0.00019 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
inspect-context 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 7d 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.
What it actually says
Context Window Inspector
Analyze everything currently loaded in this conversation's context and produce a structured, actionable report.
What to analyze
- System prompt & instructions — CLAUDE.md content, project instructions, and any system-level directives
- Loaded files — every file in context with line counts and token estimates
- Conversation history — turn count and token cost of prior messages
- Skills & plugins — active skill instructions currently loaded
- MCP server configs — tool definitions from any connected MCP servers
- Embedded documents — pasted code blocks, documents, or large text from the user
Output format
Start with a one-line status banner:
📊 Context snapshot — ~XX,XXX tokens used | ~YYY,YYY remaining | ZZ% full
Then a table sorted by estimated token usage (largest first):
| # | Source | Type | Est. Tokens | % of Budget | Keep? |
|---|---|---|---|---|---|
| 1 | src/api/routes.ts |
File | ~4,200 | 2.1% | ✅ Yes |
| 2 | Conversation (turns 1–12) | History | ~8,500 | 4.3% | ⚠️ Partial |
| 3 | CLAUDE.md |
Instructions | ~1,800 | 0.9% | ✅ Yes |
Then three sections:
🔥 Top bloat candidates
The 3 largest items that may not be needed for the current task — with a one-line reason each.
✅ Essential context
A short bullet list of items that are clearly needed and should not be touched.
💡 Quick wins
Specific, copy-paste-ready actions to immediately reduce token usage (e.g., /clear, unloading a file, splitting the conversation).
Be precise: use real file names, skill names, and turn numbers. Estimate tokens as 1 token ≈ 4 characters for English prose, slightly fewer for dense code.
$ARGUMENTS
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.
- 7d ago First seen · 49 lines · 39 tokens per session scan A 1775c5b5420e
inspect-context is a skill published in the GitHub repository msiShariful/claude-token-inspector (4 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 487 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
dream
Prunes and consolidates the project's auto-memory to keep it minimal — deletes stale, wrong, or redundant memories, merges overlapping ones into existing files, and trims the index. Strong bias against growth: never creates new memory files and never stores new facts. Verifies staleness against the current codebase…
team-memory-protocol
A shared-memory process for teams of coding agents working on the same build. It stores project knowledge, shared context, and task progress in separate files or repositories.
knowledge-wiki
A tool that turns useful lessons from coding sessions into general articles for a team wiki. A wiki is a collection of linked reference pages, and this one can be kept locally or shared through a Git repository.
magic-compact
Compact this Claude Code session.
memem-mine
Opt in to memem's event-triggered mining. New sessions are mined automatically via the Stop hook.