hook-failure-audit
Audit hook delivery health from Agent Monitor data ā balance PreToolUse vs PostToolUse (a gap means tools that started but never reported back), detect missing Stop/SubagentStop terminators (sessions/subagents that never closed), and check for stale ingestion (no recent events)
Install / Use
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill hook-failure-auditInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of hook-failure-audit
hook-failure-audit scores 81/100 on our quality scale, 2407th of 2,771 Automation skills we index.
Its SKILL.md is 3.1 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.
With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so hook-failure-audit is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit ā read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk ā read a skill before letting an agent act on it.
hook-failure-audit compared with similar skills
All 4 of these similar skills score higher than hook-failure-audit; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| hook-failure-audit (this skill)by hoangsonww | 81 | 1.0k | 55d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 10d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
Frequently asked questions
- How do I install hook-failure-audit?
- Run
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill hook-failure-audit. The install tabs above show the steps for each supported agent. - Which AI agents does hook-failure-audit work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is hook-failure-audit safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is hook-failure-audit still maintained?
- The repository was last updated about 2 months ago, so hook-failure-audit is actively maintained.
Skill content
View source on GitHubname: hook-failure-audit description: > Audit hook delivery health from Agent Monitor data ā balance PreToolUse vs PostToolUse (a gap means tools that started but never reported back), detect missing Stop/SubagentStop terminators (sessions/subagents that never closed), and check for stale ingestion (no recent events). Use when hooks look unreliable or events seem to be dropping.
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.
Output
- A check-by-check report with a PASS / WARN / FAIL marker each (ā / ā ļø / ā) and the expected-vs-observed numbers.
- Rates as percentages to 2 decimals.
- Cite exact
event_typecounts andsession_idvalues ā never fabricate. - End with an overall verdict (e.g., "4/4 checks passed" or "hook delivery DEGRADED") and the single highest-impact remediation (e.g., reinstall hooks via the dashboard Settings, or restart the server with
npm start). - Read-only: only report what the API returns. If
curlcannot reachhttp://localhost:4820, tell the user to start the dashboard withnpm startfrom the repo root.
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu ā one CLI, zero API fees.
ruflo
82.0kš The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio ā 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.9kš·ļø The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit ā see the Safety scan above for what the skill file itself contains.
