hook-inventory
Inventory hooks across the user, project, and project-local settings plus the ~/.claude/hooks scripts directory — read through the Agent Monitor Config Explorer API — and flag hooks that POST to the network or run arbitrary commands. Reads /api/cc-config/hooks and /api/cc-config/hook-scripts. Use when auditing hook safety.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill hook-inventory --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Hook Inventory Catalogue every Claude Code hook the user has configured and assess its safety — read through the Agent Monitor dashboard at `http://localhost:4820`. ## Input The user provides: **$ARGUMENTS** This may be: - empty — inventory all hooks across every scope (default). - an event name (`PreToolUse`, `PostToolUse`, `Stop`, `SubagentStop`, `SessionStart`, `SessionEnd`, `UserPromptSubmit`, `Notification`, `PreCompact`) — restrict to that event. - "scripts" — focus on the `~/.claude/hooks` handler scripts dir. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/cc-config/hooks` | `{ items:[{ scope:"user"\|"project"\|"project-local", file, exists, hooks:{ <Event>:[{ matcher, type, command, timeout }] } }] }` | | `GET /api/cc-config/hook-scripts` | `{ dir, items:[{ name, file, size, mtime }] }` — the handler scripts under `~/.claude/hooks/` | ## Report Sections ### 1. Configured hooks by scope From `/hooks`, flatten each source into `(scope, file, Event, matcher, type, command, timeout)`. Group by `scope` (user, project, project-local). Show the event, matcher, hook `type`, and the raw `command`. Note which `file` each came from so the user can edit the
- Input
- Data Sources
- Report Sections
- 1. Configured hooks by scope
- 2. Hook scripts on disk
- 3. Safety flags
- Output
What does the hook-inventory skill do?
Inventory hooks across the user, project, and project-local settings plus the ~/.claude/hooks scripts directory — read through the Agent Monitor Config Explorer API — and flag hooks that POST to the network or run arbitrary commands. Reads /api/cc-config/hooks and /api/cc-config/hook-scripts. Use when auditing hook safety.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill hook-inventory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.