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 agentmods add commands/dykyi-roman/awesome-claude-code/audit-patternsgit 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-patterns)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/audit-patterns"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-patterns.svg" alt="Measured on agentmods" 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 | $0.00090 | $0.02677 |
| Opus 5 | $0.00045 | $0.01339 |
| Sonnet 5 | $0.00018 | $0.00535 |
| Haiku 4.5 | $0.00009 | $0.00268 |
Grade A, and why
audit-patterns 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 today.
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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Patterns Audit
Perform a comprehensive design patterns audit covering stability, behavioral, creational, and integration patterns with SOLID/GRASP analysis.
Input Parsing
Parse $ARGUMENTS to extract path, level, and optional meta-instructions:
Format: <path> [level] [-- <meta-instructions>]
Arguments:
- path: Target directory or file (required, default: current directory)
- level: Audit depth - quick|standard|deep (optional, default: standard)
- -- meta-instructions: Additional focus areas or filters (optional)
Examples:
- /acc:audit-patterns ./src
- /acc:audit-patterns ./src deep
- /acc:audit-patterns ./src quick
- /acc:audit-patterns ./src -- focus on stability patterns
- /acc:audit-patterns ./src deep -- check behavioral patterns only
- /acc:audit-patterns ./src -- level:deep (backward compatible)
Parsing rules:
- Split
$ARGUMENTSby--(space-dash-dash-space) - First part = positional arguments, Second part = meta-instructions
- In positional arguments, check if last word is a valid level (
quick|standard|deep) - If level found → extract it; remaining = path
- Also accept
level:quick|standard|deepin meta-instructions (backward compatibility) - Priority: positional > meta-instruction > default (
standard) - Default path: current directory (if empty)
Target
- Path: First part of
$ARGUMENTS(before--) - Meta-instructions: Second part (after
--) — customize audit focus
If meta-instructions provided, adjust audit to:
- Focus on specific pattern categories
- Skip categories if requested
- Analyze specific patterns in depth
- Modify output format
Pre-flight Check
-
Verify the path exists:
- If
$ARGUMENTSis empty, ask user for the project path - If path doesn't exist, report error and stop
- If
-
Verify it's a PHP project:
- Check for
composer.jsonor*.phpfiles - If not a PHP project, report and stop
- Check for
Instructions
Use the acc:pattern-auditor coordinator to perform a comprehensive patterns audit:
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.
- today First seen · 301 lines · 90 tokens per session scan A 9dcd3d7c7ba2
audit-patterns is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 19d ago), licensed MIT. It adds 90 tokens to every session and 2,677 once invoked, about $0.0005 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.