config-audit

1# Config Audit
2 
3Produce a complete, data-backed audit of how the user's `~/.claude`
4configuration has grown, what overlaps, and what is risky — all read through
5the Agent Monitor dashboard at `http://localhost:4820`.
6 
7## Input
8 
9The user provides: **$ARGUMENTS**
10 
11This may be:
12- empty or "full" — audit every surface (default).
13- "skills" / "agents" / "commands" / "hooks" / "settings" — scope the audit to
14  one surface only.
15- a project path passed as `?cwd=` — to audit a project other than the
16  dashboard server's own working directory.
17 
18## Data Sources
19 
20| Endpoint | Returns |
21|----------|---------|
22| `GET /api/cc-config/overview` | `roots` + `counts` for every surface, split `{user,project}` where applicable (skills, agents, commands, outputStyles, plugins, mcpServers, hooks, memory, settingsFiles) |
23| `GET /api/cc-config/skills` | `{ items:[{ scope, name, file, size, mtime, frontmatter, preview }] }` |
24| `GET /api/cc-config/agents` | `{ items:[{ scope, name, file, size, mtime, frontmatter, preview }] }` |
25| `GET /api/cc-config/commands` | `{ items:[{ scope, name, file, size, mtime, frontmatter, preview }] }` |
26| `GET /api/cc-config/hooks` | `{ items:[{ scope, file, exists, hooks:{ <Event>:[{matcher,type,command,timeout}] } }] }` |
27| `GET /api/cc-config/settings` | `{ items:[{ scope, file, exists, data(redacted), raw_size }] }` |
28 
29## Report Sections
30 
31### 1. Surface inventory (user vs project)
32From `/overview` `counts`, print a table: one row per surface with `user`,
33…