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/usagegit 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.00018 | $0.00088 |
| Opus 5 | $0.00009 | $0.00044 |
| Sonnet 5 | $0.00004 | $0.00018 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
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 yesterday.
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 summary --project "$(basename "$PWD")" --since 7d
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.
- yesterday First seen · 7 lines · 18 tokens per session scan A d52005fd178c
usage is a command published in the GitHub repository krishnesh7/claude-usage-analytics (2 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 88 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
autobot
Launch a bot command in an isolated autobot session with its own worktree, backend, and frontend.
uxbot-aggregate
Aggregate per-task UXBot reports into an overall UX report, looking for patterns across tasks.
qabot
You are the orchestrator for the qabot workflow. QABot performs pre-merge QA analysis on the current branch, running directly in this project against the locally running server. For an isolated worktree version, use /autobot /qabot instead.
fixbot
You are the orchestrator for the fixbot workflow. Fixbot fixes a Linear issue, running directly in this project against the locally running server. For an isolated worktree version, use /autobot /fixbot instead.
qabot-report
Regenerate the QA report from existing review files.
header
Commands built into the Metabase JAR for managing your instance, including database migrations, serialization, and administrative tasks.