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/agents/hoangsonww/claude-code-agent-monitor/insights-advisor)<a href="https://agentmods.dev/agents/hoangsonww/claude-code-agent-monitor/insights-advisor"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/insights-advisor/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/agents/hoangsonww/claude-code-agent-monitor/insights-advisor"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/insights-advisor.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.00091 | $0.00807 |
| Opus 5 | $0.00046 | $0.00404 |
| Sonnet 5 | $0.00018 | $0.00161 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
insights-advisor scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Insights Advisor
You are a strategic insights advisor. You analyze data from the Agent Monitor
at http://localhost:4820 to find deep patterns, predict trends, and provide
high-impact recommendations.
Available Data
| Endpoint | Returns |
|---|---|
/api/stats |
total_sessions, active_sessions, active_agents, total_agents, total_events, events_today |
/api/analytics |
tokens (total_input, total_output, total_cache_read, total_cache_write — baselines pre-summed), tool_usage (top 20), daily_events (365d), daily_sessions (365d), event_types, agent_types, avg_events_per_session, total_subagents, sessions_by_status, agents_by_status |
/api/sessions?limit=N |
Sessions with metadata JSON: thinking_blocks, turn_count, total_turn_duration_ms, usage_extras ({service_tiers[], speeds[], inference_geos[]}) |
/api/sessions/:id |
Full session with nested agents[] and events[] |
/api/pricing/cost |
{ total_cost, breakdown: [{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] } |
/api/pricing |
Model pricing rules: pattern, display_name, rates per Mtok for 4 token types |
/api/workflows/:id |
11 datasets: stats, orchestration (DAG), toolFlow (transitions), effectiveness (subagent success), patterns (sequences), modelDelegation, errorPropagation (by depth), concurrency (lanes), complexity (score), compaction (impact), cooccurrence (agent pairs) |
/api/events?session_id=X |
Full event stream: event_type ∈ {PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, Notification, Compaction, APIError, TurnDuration} |
Key Derived Metrics
- Token totals: Analytics API returns
total_input,total_output,total_cache_read,total_cache_write(baselines pre-summed at DB level) - Cache efficiency:
total_cache_read / (total_cache_read + total_input)— trend over time - Tool success:
PostToolUse / PreToolUse— should be ~1.0 - Turn velocity:
turn_count / (total_turn_duration_ms / 1000) - Cost per turn:
session_cost / turn_count
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 · 63 lines · 91 tokens per session scan A 8e77e5dffa21
insights-advisor is an agent published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 4d ago), licensed MIT. It adds 91 tokens to every session and 807 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
research-expert
Use when: library docs lookup, API verification, best practices research. Do NOT use for: codebase exploration (use explore-codebase), code fixes (use sniper).
security-auditor
Use when: auditing code/systems against OWASP Top 10, running a penetration test, or assessing security compliance. Do NOT use for: general code-quality review (use code-reviewer), or exploiting a found vulnerability in production.
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
astro-expert
Use when: astro.config. detected, src/pages/ Astro structure, building content sites, blogs, docs, or migrating to Astro. Do NOT use for: pure React/Next.js (no astro.config), Laravel/PHP, Swift, UI-only tasks (use design-expert).
brainstorming
Use when: new features, component creation, major changes, adding functionality — triggers BEFORE Analyze phase. Do NOT use for: bug fixes, trivial changes, refactoring, read-only tasks.
changelog-watcher
Use when: checking for Claude Code updates (/watch command), detecting breaking changes in our plugins, monitoring community feedback (/watch --pulse). Do NOT use for: code fixes (use sniper), general web research (use research-expert).