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.
/plugin marketplace add krishnesh7/claude-usage-analyticsnpx agentmods add plugins/krishnesh7/claude-usage-analytics/marketplacegit clone --depth 1 https://github.com/krishnesh7/claude-usage-analyticsGrade A, and why
claude-usage-analytics 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 2d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-marketplace.json",
"name": "claude-usage-analytics",
"description": "Local-first token usage & imputed cost analytics for Claude Code.",
"owner": {
"name": "Krishnesh Pujari"
},
"plugins": [
{
"name": "claude-usage-analytics",
"description": "Local-first token usage & imputed cost analytics for Claude Code. Offline parser + SQLite + live dashboard and static reports, with session-kind/SDLC classification, secret redaction, and per-project attribution. Self-bootstrapping Python; near-zero LLM overhead.",
"author": {
"name": "Krishnesh Pujari"
},
"source": ".",
"category": "productivity"
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 20 lines scan A 30d91225d01c
claude-usage-analytics is a plugin published in the GitHub repository krishnesh7/claude-usage-analytics (2 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
hush
Trims command output, logs, and Claude's play-by-play before they pile up in the session, so long, noisy work stays quiet and readable. Install and forget — nothing to configure. Short questions with nothing to run cost a little more.
cc-statusline
Plugin marketplace listing 1 plugin: cc-statusline.
powerbi-agent-mcp
Plugin marketplace listing 1 plugin: powerbi-agent.
promptline
Local, read-only visual timeline of your Claude Code prompt history - dashboard, activity heatmap, and searchable per-project/session feed. Binds to 127.0.0.1 only, no outbound network calls, nothing written back to /.claude.
alihassanml
Developer tooling for Claude Code.
claude-code-monitor
Local usage, cost and failure dashboard for Claude Code. Auto-starts on session start; open http://localhost:8787.