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-testgit 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-test)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/audit-test"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-test.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.1 | $0.00024 | $0.02009 |
| Opus 5 | $0.00012 | $0.01005 |
| Sonnet 5 | $0.00005 | $0.00402 |
| Haiku 4.5 | $0.00002 | $0.00201 |
Grade A, and why
audit-test 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 2d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Quality Audit
Perform a comprehensive test quality audit with actionable improvement recommendations.
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-test tests/
- /acc:audit-test tests/ deep
- /acc:audit-test tests/ quick
- /acc:audit-test tests/ -- focus on Domain layer only
- /acc:audit-test tests/ deep -- focus on test smells
- /acc:audit-test tests/ -- 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)
Pre-flight Check
-
Verify the path exists:
- If
$ARGUMENTSis empty, audit current directory - If path doesn't exist, report error and stop
- If
-
Verify test infrastructure:
- Check for
phpunit.xmlorphpunit.xml.dist - Check for
tests/directory - Check for PHPUnit in
composer.json(require-dev) - If no test infrastructure found, report and suggest
/acc:generate-test
- Check for
-
Check test tooling:
- Look for coverage configuration (Xdebug/PCOV)
- Note Pest, Codeception, or other frameworks if present
Audit Levels
Level is an optional positional parameter. Default: standard.
| Level | Scope | What's Checked |
|---|---|---|
quick |
Coverage count | Class/method coverage percentage, critical untested paths |
standard |
Full analysis | Coverage gaps, test smells (15 antipatterns), naming, isolation, quality metrics |
deep |
Standard + cross-analysis | Standard + cross-test dependencies, test execution order sensitivity, fixture analysis |
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.
- 2d ago First seen · 233 lines · 24 tokens per session scan A 390e84640c1e
audit-test is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 20d ago), licensed MIT. It adds 24 tokens to every session and 2,009 once invoked, about $0.0001 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.