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/hoangsonww/Claude-Code-Agent-MonitorWrote 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/commands/hoangsonww/claude-code-agent-monitor/burn-rate)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/burn-rate"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/burn-rate/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/commands/hoangsonww/claude-code-agent-monitor/burn-rate"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/burn-rate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00020 | $0.00346 |
| Opus 5 | $0.00010 | $0.00173 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
burn-rate scanned grade A with 1 finding 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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:4820/api/analytics What it actually says
Estimate the recent daily spend trend (burn rate) for Claude Code usage from the Agent Monitor dashboard.
Fetch analytics, which includes the 365-day daily series and token totals:
curl -s http://localhost:4820/api/analytics
Use daily_sessions (365 days of { date, count }) together with per-session cost to estimate daily spend. If daily_sessions does not carry cost directly, fetch the session list to map cost to dates:
curl -s "http://localhost:4820/api/sessions?limit=200"
Then compute and print:
- Last 7 days vs. prior 7 days — total spend in each window, and the change as a percent with ▲ (up) / ▼ (down).
- 7-day burn rate — average daily spend over the last 7 days, as USD to 4 decimal places, plus a simple 30-day projection (
avg_daily × 30). - Per-day mini-trend — one line per day for the last 7 days:
<date> — $<spend to 4dp>with a ▲/▼ vs. the prior day.
Currency as USD to 4 decimal places. Keep it to these three blocks — no long analysis.
If session dates and costs cannot be aligned precisely, state the approximation you made in one line rather than fabricating exact daily figures. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.
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.
- 13d ago First seen · 29 lines · 20 tokens per session scan A 3ee9654efe21
burn-rate is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 346 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
secular-trends
Secular technology trends analysis — technology adoption cycles, disruption risk, strategic positioning.
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
earnings
Post-earnings analysis for a stock — fast in-chat summary card by default, full Markdown research report on request.
budget
Marks the cheapest Claude model and effort that still clears this task with high confidence. Still shows the full Budget, Optimal, and Splurge spread.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.