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/cost-today)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/cost-today"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/cost-today/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/cost-today"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/cost-today.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.00016 | $0.00315 |
| Opus 5 | $0.00008 | $0.00158 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
cost-today 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 12d 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/pricing/cost What it actually says
Print a quick cost snapshot from the Agent Monitor dashboard pricing engine.
The user's scope is $ARGUMENTS (default today if empty; accepts today or week).
Fetch the fleet-wide cost breakdown:
curl -s http://localhost:4820/api/pricing/cost
This returns { total_cost, breakdown: [{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }.
Then print, concisely:
- Total cost —
total_costas USD to 4 decimal places, labeled with the scope ($ARGUMENTS). - Per-model one-liners — one line per entry in
breakdown, sorted bycostdescending:<model> — $<cost to 4dp> (in <input_tokens>, out <output_tokens>, cacheR <cache_read_tokens>, cacheW <cache_write_tokens>)
Keep token counts with thousands separators. No tables, no preamble — just the total and the per-model lines.
Note: the endpoint returns lifetime totals; if the user asked for today or week and the data is not scoped, say so in one line rather than fabricating a windowed number. 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.
- 12d ago First seen · 27 lines · 16 tokens per session scan A fa7830ce6553
cost-today is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 315 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.