Hook Failure Audit

CommunityPopular

hoangsonww

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). Use when hooks look unreliable or events seem to be dropping.

Overview

Publisher	hoangsonww
Repository	`Claude-Code-Agent-Monitor`
Skill name	`hook-failure-audit`
Stars	1.1K
Forks	260
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by hoangsonww on GitHub. Read the source before you install it.

Installation

Install the Hook Failure Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-quality/skills/hook-failure-audit
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-quality/skills/hook-failure-audit

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/Claude-Code-Agent-Monitor
mkdir -p .claude/skills
cp -r /tmp/Claude-Code-Agent-Monitor/plugins/ccam-quality/skills/hook-failure-audit .claude/skills/hook-failure-audit

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hook Failure Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hook Failure Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hook Failure Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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_type counts and session_id values — 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 curl cannot reach http://localhost:4820, tell the user to start the dashboard with npm start from the repo root.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Hook Failure Audit AI skill do?

Why use Hook Failure Audit on TypingMind?

Because you install it once and use it with any model. Hook Failure Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hook Failure Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-quality/skills/hook-failure-audit. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Hook Failure Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hook Failure Audit?

As many as you like. As long as a model supports skills, you can use Hook Failure Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hook Failure Audit AI skill free?

Yes. It is published on GitHub by hoangsonww under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Faiss

NousResearch

OrganizationPopular

Fast vector similarity search at billion scale.

Serving Llms Vllm

vLLM: high-throughput LLM serving, OpenAI API, quantization.

Huggingface Hub

HuggingFace hf CLI: search/download/upload models, datasets.

Pytorch Lightning

Clean training loops with built-in distributed support.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Hook Failure Audit

Input

Data Sources

Report Sections

1. PreToolUse / PostToolUse Balance

2. Missing Terminators

3. Stale Ingestion

4. Localize

Output

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now