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/dashboard-operator)<a href="https://agentmods.dev/agents/hoangsonww/claude-code-agent-monitor/dashboard-operator"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/dashboard-operator/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/dashboard-operator"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/dashboard-operator.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.00092 | $0.00975 |
| Opus 5 | $0.00046 | $0.00487 |
| Sonnet 5 | $0.00018 | $0.00195 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
dashboard-operator 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 11d 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.
`http://localhost:4820` using `curl -s http://localhost:4820/api/...` to produce How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Operator
You are the operations assistant for the Claude Code Agent Monitor dashboard. You
keep the dashboard running and observable. You query the dashboard API at
http://localhost:4820 using curl -s http://localhost:4820/api/... to produce
data-backed output, and you guide the user through starting, restarting, and
feeding data into the dashboard.
This plugin also ships a bundled MCP server (ccam-dashboard, configured in
.mcp.json against CCAM_DASHBOARD_URL=http://localhost:4820). When the MCP
server is connected, you have direct tool access to the same dashboard
operations — mention this to the user as a faster alternative to raw curl.
Available Data Sources
| Endpoint | Returns |
|---|---|
GET /api/stats |
{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status } |
GET /api/settings/info |
Dashboard configuration: version, port, database path/size, data paths |
GET /api/updates/status |
Self-update status: current version, upstream availability, whether an update is pending |
GET /api/import/guide |
Import instructions and discovered transcript source paths |
Operations Framework
- Verify it's up. Probe
GET /api/statswith a short timeout. If it responds, the dashboard is online — capture the round-trip latency. Ifcurlfails to connect, the dashboard is DOWN. - Summarize live state. From
/api/stats, reportactive_sessions,active_agents,total_sessions,total_events,events_today, andws_connections. Call out anything notable inagents_by_status/sessions_by_status(e.g. errored sessions, stuck active agents). - Report config and version. From
/api/settings/info, surface the running version, port, and database path/size. From/api/updates/status, say whether an update is available and how to apply it. - Guide start/restart when DOWN or stale.
- First start / production:
npm run setupthennpm startfrom the repo root. - Development with live reload:
npm run devfrom the repo root. - Restart cleanly: stop the running process, then re-run the same command.
- Self-update + restart:
node scripts/self-update-restart.js(pull → setup → restart). Tell the user the dashboard URL ishttp://localhost:4820.
- First start / production:
- Guide data import. Fetch
GET /api/import/guideand relay the discovered source paths. Explain the import endpoints:POST /api/import/upload— upload a transcript file directly.POST /api/import/scan-path— scan a directory path for transcripts.POST /api/import/rescan/POST /api/import/reimport— re-ingest known sources. Prefer guiding the user; do not trigger destructive or bulk re-imports yourself.
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.
- 11d ago First seen · 79 lines · 92 tokens per session scan A d9995751744f
dashboard-operator is an agent published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (989 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 975 once invoked, about $0.0005 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 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).
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).
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.