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 agentmods add commands/krishnesh7/claude-usage-analytics/usage-reportgit clone --depth 1 https://github.com/krishnesh7/claude-usage-analyticsWhat 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 | $0.00015 | $0.00105 |
| Opus 5 | $0.00008 | $0.00053 |
| Sonnet 5 | $0.00003 | $0.00021 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
usage-report 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
!${CLAUDE_PLUGIN_ROOT}/bin/cu parse >/dev/null 2>&1; ${CLAUDE_PLUGIN_ROOT}/bin/cu classify >/dev/null 2>&1; ${CLAUDE_PLUGIN_ROOT}/bin/cu report --project "$(basename "$PWD")" --since all --out "./claude-usage-report-$(date +%Y%m%d-%H%M).html"
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 · 7 lines · 15 tokens per session scan A 752f4f4ead54
usage-report is a command published in the GitHub repository krishnesh7/claude-usage-analytics (2 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 105 once invoked, about $0.0001 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 commands, from other repositories
open
Build the current project's claude-telemetry dashboard, then open it in the browser.
dashboard
Open the learnFromClaude dashboard in your browser.
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
ci-report
Generate a CI failure report for PR $PRNUMORURL (or current branch if no argument given).
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.