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-comparegit 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.00026 | $0.00121 |
| Opus 5 | $0.00013 | $0.00060 |
| Sonnet 5 | $0.00005 | $0.00024 |
| Haiku 4.5 | $0.00003 | $0.00012 |
Grade A, and why
usage-compare 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
Display the feature comparison document for the claude-usage-tracker plugin.
Run:
cat "${CLAUDE_PLUGIN_ROOT}/docs/COMPARISON.md"
Render the output as formatted Markdown. After displaying it, ask the user if there is a specific capability they want to explore or enable (e.g. cost imputation, project registration, SDLC stage tagging, or the live dashboard).
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 · 16 lines · 26 tokens per session scan A a66f482b83c9
usage-compare is a command published in the GitHub repository krishnesh7/claude-usage-analytics (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 121 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.
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.
reprobot
You are the orchestrator for the reprobot workflow. ReproBot attempts to reproduce a reported bug against the locally running server, classifies the result, and optionally writes a failing test. For an isolated worktree version, use /autobot /reprobot instead.
autobot-stop
Stop an autobot session (kill tmux and dev environment, but keep the worktree).
qabot-report
Regenerate the QA report from existing review files.
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.