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.
git clone --depth 1 https://github.com/fschmutz/claude-usage-panelWrote 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/mcp/fschmutz/claude-usage-panel/claude-usage)<a href="https://agentmods.dev/mcp/fschmutz/claude-usage-panel/claude-usage"><img src="https://agentmods.dev/badge/mcp/fschmutz/claude-usage-panel/claude-usage/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/mcp/fschmutz/claude-usage-panel/claude-usage"><img src="https://agentmods.dev/badge/mcp/fschmutz/claude-usage-panel/claude-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-usage 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 4d 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
{
"claude-usage": {
"command": "npx",
"args": [
"-y",
"github:fschmutz/claude-usage-panel#v3.11.0"
]
}
}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.
- 4d ago Changed 52bbbe5e711f
- 17d ago Changed f99230b67a0a
- 20d ago Changed ff925742b3f8
- 21d ago Changed 4d550274cc93
- 22d ago Changed 51fff9ba0465
- 1mo ago Changed 688fecde3b05
- 2mo ago First seen · 9 lines scan A 95c54aa101fe
claude-usage is an MCP server published in the GitHub repository fschmutz/claude-usage-panel (7 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
memocall
Recall past Claude Code conversations from any project as clean, compact Markdown. Runs locally from the memocall npm package.
mcp-bash-server
MCP server "mcp-bash-server" as configured in uditk2/mcp-bash-server. Runs locally from the mcp-bash-server Python package.
sn-patterns-mcp
ServiceNow Discovery pattern intelligence MCP server — Python NDL parser/writer + 28 MCP tools (read, search, validate, author, surgical-edit, emulate). Runs locally from the sn-patterns-mcp Python package.
tracer
MCP server "tracer" as configured in aiquilibria/contAIned. Runs contained.tracer_mcp with python3.
wefact-mcp
MCP server for WeFact — let Claude (Desktop, Code, Cursor) read and modify your WeFact administration via the v2 API. Runs locally from the wefact-mcp Python package.
pr-reviewer
AI-powered code review for GitHub & GitLab. Works with any LLM: GPT-4o, Claude, Llama, Gemini, Ollama. Free, open source. Runs locally from the pr-reviewer Python package.