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-psr)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/audit-psr"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-psr/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-psr"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-psr.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.00039 | $0.02105 |
| Opus 5 | $0.00019 | $0.01052 |
| Sonnet 5 | $0.00008 | $0.00421 |
| Haiku 4.5 | $0.00004 | $0.00211 |
Grade A, and why
audit-psr 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PSR Compliance Audit
Perform a comprehensive PSR compliance 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-psr ./src
- /acc:audit-psr ./src deep
- /acc:audit-psr ./src quick
- /acc:audit-psr ./src -- focus on PSR-12 only
- /acc:audit-psr ./src deep -- focus on interfaces
- /acc:audit-psr ./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)
Pre-flight Check
-
Verify the path exists:
- If
$ARGUMENTSis empty, audit current directory - 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
-
Check PSR tooling:
- Look for
.php-cs-fixer.php,phpcs.xml,phpstan.neon - Look for PSR packages in
composer.json(psr/log, psr/cache, psr/http-message, etc.) - Note available vs missing tooling in report
- Look for
Audit Levels
Level is an optional positional parameter. Default: standard.
| Level | Scope | What's Checked |
|---|---|---|
quick |
Structure only | declare(strict_types=1), namespace conventions, basic naming |
standard |
Full analysis | PSR-1/12 coding style, PSR-4 autoloading, interface detection, file:line references |
deep |
Standard + quality | Standard + PSR interface implementation quality, method signatures, return types, docblock compliance |
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 · 222 lines · 39 tokens per session scan A 6e3fdd9bd4ba
audit-psr is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 23d ago), licensed MIT. It adds 39 tokens to every session and 2,105 once invoked, about $0.0002 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
review-uv-script
Review uv Python script for PEP 723 compliance and best practices.
rust-review
Lightweight Rust code review using clippy.
review
Comprehensive code review for blz changes.
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
sinatra-review
Review Sinatra code for security issues, performance problems, route conflicts, and framework best practices.
cli-review
Review Rust CLI applications for UX, error handling, testing, and cross-platform compatibility.