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.
git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/commands/dykyi-roman/awesome-claude-code/audit-claude-components)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/audit-claude-components"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-claude-components/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/commands/dykyi-roman/awesome-claude-code/audit-claude-components"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-claude-components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00058 | $0.08128 |
| Opus 5 | $0.00029 | $0.04064 |
| Sonnet 5 | $0.00012 | $0.01626 |
| Haiku 4.5 | $0.00006 | $0.00813 |
Grade A, and why
audit-claude-components scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 1,003 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Configuration Audit
Perform a comprehensive audit of the .claude/ folder in the current project.
Input Parsing
Parse $ARGUMENTS to extract level and optional meta-instructions:
Format: [level] [-- <meta-instructions>]
Arguments:
- level: Audit depth - quick|standard|deep (optional, default: standard)
- -- meta-instructions: Additional focus areas or filters (optional)
Examples:
- /acc:audit-claude-components
- /acc:audit-claude-components deep
- /acc:audit-claude-components quick
- /acc:audit-claude-components -- focus on God-Agent detection
- /acc:audit-claude-components deep -- check only commands
- /acc:audit-claude-components -- level:deep (backward compatible)
Parsing rules:
- Split
$ARGUMENTSby--(space-dash-dash-space) - First part = positional arguments, Second part = meta-instructions
- If first positional argument is
quick|standard|deep→ this is level - Also accept
level:quick|standard|deepin meta-instructions (backward compatibility) - Priority: positional > meta-instruction > default (
standard)
If meta-instructions provided, adjust audit to:
- Focus on specific component types (commands/agents/skills)
- Prioritize specific checks (God-Agent, cross-references, etc.)
- Skip certain analysis phases
Pre-flight Check
- Check if
.claude/folder exists in the current working directory - If missing, skip to Missing Configuration section
Audit Process
Step 1: Scan Structure
Discover all components:
.claude/
├── commands/ # Slash commands (*.md)
├── agents/ # Custom agents (*.md)
├── skills/ # Skills (name/SKILL.md)
├── plans/ # Plan files
├── settings.json # Project settings
├── settings.local.json # Local settings (gitignored)
├── CLAUDE.md # Project instructions
└── README.md # Documentation
Use Glob to find:
.claude/commands/*.md.claude/agents/*.md.claude/skills/*/SKILL.md.claude/settings.json.claude/settings.local.json.claude/CLAUDE.md.claude/rules/*.md.claude-plugin/plugin.jsonCLAUDE.md(project root)CLAUDE.local.md(project root)
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.
- 5d ago First seen · 1,003 lines · 0 tokens per session scan A 7e68f239e507
audit-claude-components is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 23d ago), licensed MIT. It adds 58 tokens to every session and 8,128 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.