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 mcp-auditgit 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/mcp-audit)<a href="https://agentmods.dev/skills/msishariful/claude-token-inspector/mcp-audit"><img src="https://agentmods.dev/badge/skills/msishariful/claude-token-inspector/mcp-audit/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/msishariful/claude-token-inspector/mcp-audit"><img src="https://agentmods.dev/badge/skills/msishariful/claude-token-inspector/mcp-audit.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.00053 | $0.00643 |
| Opus 5 | $0.00026 | $0.00321 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
mcp-audit 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Audit
You are an MCP efficiency auditor. Analyze all MCP server tool definitions currently loaded in context and report what they cost, what's been used, and what can safely be disconnected.
What to analyze
For each MCP server detected in context:
- Server name and connection type (stdio, SSE, etc.)
- Tool count — how many tools it exposes
- Token cost — the definition size of all its tool schemas combined
- Usage in this conversation — which tools have actually been called
- Relevance to the current task — does the current task need these tools?
Estimation method
MCP tool definitions include the tool name, description, and JSON schema for parameters. Estimate:
- Simple tool (name + short description + 1–3 params): ~150–300 tokens
- Medium tool (description + schema with 5–10 params): ~400–700 tokens
- Complex tool (nested schemas, many params, long descriptions): ~800–2,000 tokens
Sum all tools per server for that server's total token cost.
Output format
Open with a summary line:
🔌 {N} MCP server(s) loaded — ~{total} tokens in tool definitions
Then a table sorted by token cost (highest first):
| Server | Tools | Est. Tokens | Used This Session | Relevant? |
|---|---|---|---|---|
filesystem |
8 | ~2,400 | ✅ 3 tools used | ✅ Yes |
github |
15 | ~6,200 | ❌ None | ⚠️ Maybe |
slack |
12 | ~4,800 | ❌ None | 🔴 No |
Then three sections:
🔴 Disconnect these — not used, not needed
For each: server name, token cost saved, why it's not relevant to the current task, and the exact command to disconnect it.
🟡 Questionable — loaded but unused
For each: server name, token cost, what it's for, and whether it might be needed later in this task.
🟢 Keep — actively used or clearly needed
Compact list. No elaboration.
💡 Optimization moves
- Total tokens recoverable if recommendations are followed
- Suggest disabling auto-connect for servers that are rarely needed
- Note if any single server dominates the MCP token budget
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 · 75 lines · 53 tokens per session scan A 565eb2086cd6
mcp-audit is a skill published in the GitHub repository msiShariful/claude-token-inspector (4 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 643 once invoked, about $0.0003 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
docs-drift
Documentation-drift audit for this plugin monorepo. Audit either each scoped plugin's unreleased changelog claims or its latest shipped release from the previous reachable plugin-name--v tag, then verify that plugin READMEs, docs, CLAUDE.md or AGENTS.md files, and root documentation tell the truth for the matching…
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.
magic-compact
Compact this Claude Code session.