Claude Code Agent Monitor is a dashboard that records and displays activity from Claude Code and Codex coding-agent sessions, including tool use and subagent coordination. It is for people who need live visibility into agent work through a web interface or native desktop app. The catalogue entries extend Claude Code with skills, commands, agents, plugins, instructions, hooks, and settings related to the monitor.
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.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill hook-failure-auditgit 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/skills/hoangsonww/claude-code-agent-monitor/hook-failure-audit)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/hook-failure-audit"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/hook-failure-audit/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/skills/hoangsonww/claude-code-agent-monitor/hook-failure-audit"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/hook-failure-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.00767 |
| Opus 5.5 | $0.00029 | $0.00307 |
| Sonnet 5.5 | $0.00015 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
hook-failure-audit 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 1mo 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.
- Read-only: only report what the API returns. If `curl` cannot reach `http://localhost:4820`, tell the user to start the dashboard with `npm start` from the repo root. How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Failure Audit
Assess whether the hook pipeline is delivering events reliably, using the event counts and stream the dashboard already has. This is about delivery health (missing/dropped events), not about why a model errored.
Input
The user provides: $ARGUMENTS
This may be:
- empty or "all" — run every check (default)
- "balance" — PreToolUse/PostToolUse balance only
- "terminators" — missing Stop/SubagentStop only
- "freshness" — stale-ingestion check only
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/analytics |
event_types (counts per type: PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd), daily_events (365d), total_subagents, sessions_by_status — fleet-wide delivery balance |
GET /api/stats |
total_sessions, total_agents, total_events, events_today — expected terminator counts and recency |
GET /api/events?session_id=X |
Per-session stream — confirm which sessions are missing a PostToolUse, Stop, or SubagentStop |
Report Sections
1. PreToolUse / PostToolUse Balance
From GET /api/analytics event_types: gap = PreToolUse − PostToolUse. A positive gap means tools whose completion hook never arrived. Report the gap as a count and as a percentage of PreToolUse. A healthy pipeline keeps this near 0%.
2. Missing Terminators
Compare Stop count against completed sessions (sessions_by_status) and SubagentStop against total_subagents/total_agents (from /api/stats). A shortfall means sessions or subagents that ran but never emitted a closing hook — likely dropped delivery or a crashed handler. Report expected vs observed for each.
3. Stale Ingestion
Check events_today from /api/stats and the tail of daily_events from analytics. If recent days are empty while sessions exist, ingestion has stalled. Report the most recent day with events and how long ago that was.
4. Localize
For the sessions with the largest gaps or missing terminators, pull GET /api/events?session_id=X and confirm which specific hook types are absent. List the offending session IDs.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 56 lines · 73 tokens per session scan A 02967e1035f4
hook-failure-audit is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (1,124 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 767 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
code-remediate
Collect and resolve selected findings in one pass, then verify; bare PR targets use online items, while PR +review authorizes matching review evidence and any needed review step.
challenge-resolve
Independently review and fix a bounded task through convergence rounds, with evidence-backed closure and explicit stop/remediation decisions. Use only when the user explicitly requests an adversarial review-and-fix loop over an existing implementation, feature, problem, or diff; not for ordinary review (code-review)…
php-quality-tooling
Use when setting up PHPStan, Rector, or PHP-CS-Fixer on a non-Laravel PHP project, incl. CI wiring. Do NOT use for Laravel (Pint/Larastan), tests, or syntax.
Rig Optimize
Improve a measured performance metric in guarded rounds, keeping only changes that beat the baseline noise and pass every correctness gate.
Rig Investigate
Reproduce a failure and narrow it to an evidence-backed root cause before fixing.
Rig Doctor
Check opencode-rig install health and report exact remediation steps.