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/workflow)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/workflow"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/workflow/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/workflow"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/workflow.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.00378 |
| Opus 5 | $0.00009 | $0.00189 |
| Sonnet 5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
workflow 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 6d 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.
The session id is **$ARGUMENTS**. If empty, fetch `curl -s 'http://localhost:4820/api/sessions?limit=1'` and use the most recent session, stating which id you picked. If the dashboard is unreachable, tell the user to sta What it actually says
Summarize the Agent Monitor workflow intelligence for a session from http://localhost:4820.
The session id is $ARGUMENTS. If empty, fetch curl -s 'http://localhost:4820/api/sessions?limit=1' and use the most recent session, stating which id you picked. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.
Fetch the workflow intelligence:
curl -s http://localhost:4820/api/workflows/$ARGUMENTS
This returns 11 datasets: stats, orchestration, toolFlow, effectiveness, patterns, modelDelegation, errorPropagation, concurrency, complexity, compaction, cooccurrence.
Print, concisely:
- Header — session id, total agents, max depth, and total tool calls (from
stats/orchestration). - Complexity — the numeric
complexityscore and what drives it (depth, breadth, tool diversity). - Top patterns — up to 5 recurring sequences from
patterns, each assequence ×frequency, sorted by frequency descending. - Quick signals — one line each: concurrency lane count (
concurrency), subagent success rate (effectiveness), and total errors with origin depth (errorPropagation).
Keep it terse — this is a one-shot. Cite only numbers returned by the API; for deeper analysis point the user at the dag-map, delegation-audit, concurrency-report, or error-propagation skills.
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.
- 6d ago First seen · 26 lines · 18 tokens per session scan A d8097b61fdd2
workflow is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (987 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 378 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.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.
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.