hook-inventory

1# Hook Inventory
2 
3Catalogue every Claude Code hook the user has configured and assess its safety —
4read through the Agent Monitor dashboard at `http://localhost:4820`.
5 
6## Input
7 
8The user provides: **$ARGUMENTS**
9 
10This may be:
11- empty — inventory all hooks across every scope (default).
12- an event name (`PreToolUse`, `PostToolUse`, `Stop`, `SubagentStop`,
13  `SessionStart`, `SessionEnd`, `UserPromptSubmit`, `Notification`,
14  `PreCompact`) — restrict to that event.
15- "scripts" — focus on the `~/.claude/hooks` handler scripts dir.
16 
17## Data Sources
18 
19| Endpoint | Returns |
20|----------|---------|
21| `GET /api/cc-config/hooks` | `{ items:[{ scope:"user"\|"project"\|"project-local", file, exists, hooks:{ <Event>:[{ matcher, type, command, timeout }] } }] }` |
22| `GET /api/cc-config/hook-scripts` | `{ dir, items:[{ name, file, size, mtime }] }` — the handler scripts under `~/.claude/hooks/` |
23 
24## Report Sections
25 
26### 1. Configured hooks by scope
27From `/hooks`, flatten each source into `(scope, file, Event, matcher, type,
28command, timeout)`. Group by `scope` (user, project, project-local). Show the
29event, matcher, hook `type`, and the raw `command`. Note which `file` each came
30from so the user can edit the right one.
31 
32### 2. Hook scripts on disk
33From `/hook-scripts`, list each file in `~/.claude/hooks/` with `name`, `size`
34(KB), and `mtime`. Cross-reference: flag scripts referenced by a hook `command`
35but missing from disk, and scripts on disk that no configured hook calls
36(orphaned).
37…