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/insights)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/insights"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/insights/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/insights"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/insights.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.00015 | $0.00403 |
| Opus 5 | $0.00008 | $0.00201 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
insights 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` → total_sessions, active_sessions, active_agents, total_events, events_today, agents_by_status, sessions_by_status. What it actually says
Produce the top 3 insights about Claude Code usage right now, each backed by real numbers from the Agent Monitor dashboard.
-
Fetch high-level state:
curl -s http://localhost:4820/api/stats→ total_sessions, active_sessions, active_agents, total_events, events_today, agents_by_status, sessions_by_status.curl -s http://localhost:4820/api/analytics→ tokens (total_input/total_output/total_cache_read/total_cache_write), tool_usage (top 20), daily_events (365d), daily_sessions (365d), event_types, avg_events_per_session, total_subagents.
-
Derive signal, citing exact field values:
- Cache hit rate =
total_cache_read / (total_cache_read + total_input). - Activity trend: compare the last 7 days of
daily_sessions/daily_eventsagainst the prior 7. - Concentration: the single most-used tool and most-frequent
event_type, with its share of the total. - Error pressure:
APIErrorshare of events; subagent fan-out viatotal_subagentsandavg_events_per_session.
- Cache hit rate =
-
Pick the 3 most decision-relevant findings (biggest cost lever, sharpest trend, or clearest anomaly). For each print:
- A one-line headline with the supporting number.
- Why it matters in one sentence.
- One concrete action.
Output rules: rank by impact (most important first); currency in USD to 4 decimals; rates as percentages to 2 decimals; use ▲/▼ for trend direction; cite only fields the API returned — never fabricate. 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.
- 9d ago First seen · 23 lines · 15 tokens per session scan A f15018bf8f54
insights is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 403 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
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
prompt
Create or optimize prompts using best practices.
watch
Check for Claude Code updates, detect breaking changes, analyze plugin compatibility, and optionally gather community pulse via Exa.
design-audit
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
fix-pr-comments
Systematically resolve Pull Request review comments using gh CLI to fetch comments and apply requested changes.
amend
Amend last commit safely. Use for amend, fix last commit, update commit, modify commit.