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/health)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/health"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/health/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/health"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/health.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.00018 | $0.00370 |
| Opus 5 | $0.00009 | $0.00185 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
health 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 9d 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/stats What it actually says
Print a single reliability verdict for Claude Code usage from the Agent Monitor
dashboard at http://localhost:4820. No arguments.
-
Fetch state:
curl -s http://localhost:4820/api/stats curl -s http://localhost:4820/api/analyticsFrom
stats:total_events,events_today,sessions_by_status. Fromanalytics:event_types(PreToolUse, PostToolUse, APIError). -
Derive two reliability signals:
- Error rate =
APIError / total_events(percentage, 2 decimals). - Tool-failure rate =
(PreToolUse − PostToolUse) / PreToolUse(percentage).
- Error rate =
-
Pick the verdict from the worse of the two signals:
- OK — error rate ≤ 1% and tool-failure rate ≤ 1%.
- DEGRADED — either is in 1–5%.
- FAILING — either exceeds 5%.
-
Print exactly one line:
Reliability: <OK|DEGRADED|FAILING> — errors X.XX%, tool failures Y.YY% (N events)Prefix with ✅ (OK), ⚠️ (DEGRADED), or ❌ (FAILING).
Output rules: cite only fields the API returned — never fabricate. One line only;
no extra prose. If curl cannot reach http://localhost:4820, print
Reliability: UNKNOWN — dashboard unreachable; 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.
- 9d ago First seen · 32 lines · 18 tokens per session scan A d78d92b3b65d
health is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 370 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.