Config Audit
Run a full audit of the user's Claude Code configuration via the Agent Monitor Config...
Install
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill config-audit -g -a claude-code -y- Repository
- hoangsonww/Claude-Code-Agent-Monitor1.1k
- Category
- AI and agents
- Updated
- 5d ago
- License
- MIT
- Context cost
- Lightabout 875 tokens
- Runs scripts
- No, instructions only
What it does
Run a full audit of the user's Claude Code configuration via the Agent Monitor Config Explorer API: counts per surface (user vs project), duplicate or overlapping skills and subagents, hooks that run shell commands, and which surfaces are read-only vs mutable. Reads /api/cc-config/overview, /skills, /agents, /commands, /hooks, and /settings. Use when reviewing your Claude Code setup for sprawl, duplication, or risk.
Config Audit
Produce a complete, data-backed audit of how the user's ~/.claude
configuration has grown, what overlaps, and what is risky, all read through
the Agent Monitor dashboard at http://localhost:4820.
Input
The user provides: $ARGUMENTS
This may be:
- empty or "full", audit every surface (default).
- "skills" / "agents" / "commands" / "hooks" / "settings", scope the audit to one surface only.
- a project path passed as
?cwd=, to audit a project other than the dashboard server's own working directory.
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/cc-config/overview | roots + counts for every surface, split {user,project} where applicable (skills, agents, commands, outputStyles, plugins, mcpServers, hooks, memory, settingsFiles) |
GET /api/cc-config/skills | { items:[{ scope, name, file, size, mtime, frontmatter, preview }] } |
GET /api/cc-config/agents | { items:[{ scope, name, file, size, mtime, frontmatter, preview }] } |
GET /api/cc-config/commands | { items:[{ scope, name, file, size, mtime, frontmatter, preview }] } |
GET /api/cc-config/hooks | { items:[{ scope, file, exists, hooks:{ <Event>:[{matcher,type,command,timeout}] } }] } |
GET /api/cc-config/settings | { items:[{ scope, file, exists, data(redacted), raw_size }] } |
Report Sections
1. Surface inventory (user vs project)
From /overview counts, print a table: one row per surface with user,
project, and total columns. Cover skills, agents, commands, output-styles,
plugins (with enabled/disabled), marketplaces, MCP servers, hooks
(user/project/project-local), memory, and settings files. Echo the resolved
roots so the user knows which claudeHome/project was inspected.
