Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill config-auditgit clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-MonitorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/config-audit)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/config-audit"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/config-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/config-audit"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/config-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 65 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00094 | $0.01031 |
| Opus 5 | $0.00047 | $0.00515 |
| Sonnet 5 | $0.00019 | $0.00206 |
| Haiku 4.5 | $0.00009 | $0.00103 |
Grade A, and why
config-audit scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
network egress (`curl`, `wget`, `http`, `nc`) or run unbounded with no How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
2. Duplicate & overlapping skills + agents
Fetch /skills and /agents. Detect:
- Name collisions across scope — same
nameat both user and project scope (project shadows user). List bothfilepaths. - Near-duplicates — entries whose
frontmatter.description/previewdescribe the same job. Group them and recommend keeping one.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 80 lines · 94 tokens per session scan A e437a31462b0
config-audit is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 94 tokens to every session and 1,031 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
code-remediate
Apply selected review fixes; bare PR targets use current online items, while PR +review adds the latest matching artifact.
nodejs-expert
Expert-level Node.js backend development with Express, async patterns, streams, performance optimization, and production best practices. Use when the user mentions JavaScript, backend, Express, or async, or when the task involves Modern Node.js Features, Express Framework, File System Operations, or HTTP Requests.
optimize
Optimize a measurable metric with bounded iterations, guardrails, and regression gates.
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
laravel-blade
Create Blade templates with components, slots, layouts, and directives. Use when building views, reusable components, or templating.
laravel-eloquent
Use when working with database models — Eloquent ORM, PHP attributes, relationships, queries, observers, or factories in Laravel 13.