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/errors)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/errors"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/errors.svg" alt="Measured on agentmods" 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.00013 | $0.00323 |
| Opus 5 | $0.00006 | $0.00161 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
errors 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 3d 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/events?limit=300 What it actually says
List the most recent Claude Code errors from the Agent Monitor dashboard at
http://localhost:4820. $ARGUMENTS is the number of errors to show (default 10).
-
Pull recent events and keep only API errors:
curl -s http://localhost:4820/api/events?limit=300Filter the array to
event_type == "APIError". (If$ARGUMENTSis a number, show that many; otherwise show 10.) If none are found, also checkcurl -s http://localhost:4820/api/analyticsevent_types.APIErrorto confirm the true total and say "no recent APIError events (N total all-time)". -
For each error, newest first, print one line:
timestamp · session_id · summary— using thetimestamp,session_id, andsummaryfields exactly as returned (trim long summaries to ~100 chars). -
End with a one-line tally: total APIErrors shown and the most-affected
session_id.
Output rules: cite only fields the API returned — never fabricate an error or a
cause. Keep it to the list plus the tally; no extra prose. If curl cannot reach
http://localhost:4820, tell the user to start the dashboard 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.
- 3d ago First seen · 29 lines · 13 tokens per session scan A 81e8f080cff3
errors is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (975 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 323 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-09-03.
Other commands, from other repositories
deep-code-analysis
Comprehensive codebase investigation using research-expert for documentation, explore-codebase for structure, and deep analysis. Perfect for understanding complex systems.
watch
Check for Claude Code updates, detect breaking changes, analyze plugin compatibility, and optionally gather community pulse via Exa.
fix
Quick bugfix commit. Use for fix bug, bugfix, patch, hotfix, correct error.
fix-zh
A bug-fixing command that analyses a software problem and responds in Chinese.
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.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.