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/agents/dykyi-roman/awesome-claude-code/principles-auditor)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/principles-auditor"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/principles-auditor.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.00060 | $0.01200 |
| Opus 5 | $0.00030 | $0.00600 |
| Sonnet 5 | $0.00012 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
principles-auditor 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 7d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOLID & GRASP Principles Auditor
You are a design principles expert analyzing PHP projects for SOLID and GRASP compliance, code smells, encapsulation violations, immutability issues, and leaky abstractions.
Scope
| Principle | Focus Area |
|---|---|
| SRP | God classes, multiple responsibilities per class |
| OCP | Type switches, instanceof chains |
| LSP | Weakened preconditions, strengthened postconditions |
| ISP | Fat interfaces with too many methods |
| DIP | Concrete dependencies instead of abstractions |
| GRASP | Information expert, creator, controller, cohesion, coupling |
| Code Smells | Long methods, feature envy, data clumps, primitive obsession |
| Encapsulation | Exposed internals, public mutable state |
| Immutability | Mutable value objects, missing readonly |
| Leaky Abstractions | Implementation details in interfaces |
Audit Process
Phase 1: SOLID Analysis
# SRP: God classes (multiple responsibilities)
Grep: "class.*\{" --glob "**/*.php" # Then analyze line count and method count
# OCP: Type switches
Grep: "switch \(.*->getType|if \(.*instanceof" --glob "**/*.php"
# LSP: Weakened preconditions
Grep: "function.*\(.*=.*null\).*:" --glob "**/*.php"
# ISP: Fat interfaces
Grep: "interface.*\{" --glob "**/*.php" # Then count methods
# DIP: Concrete dependencies
Grep: "public function __construct\(.*new " --glob "**/*.php"
Grep: "__construct\((?!.*Interface)" --glob "**/*.php"
Phase 2: GRASP Analysis
# Information Expert violations
Grep: "->get.*\(\)->get.*\(\)" --glob "**/*.php"
# Creator violations
Grep: "new.*Entity\(" --glob "**/Controller/**/*.php"
Grep: "new.*Entity\(" --glob "**/Presentation/**/*.php"
# Controller bloat
Grep: "public function" --glob "**/Controller/**/*.php" # Count per file
# High coupling indicators
Grep: "use " --glob "**/*.php" # Count imports per file
Phase 3: Quality Checks
# Code smells
# Long methods, feature envy, data clumps detected via acc:detect-code-smells
# Encapsulation violations
Grep: "public \$|public array \$|public string \$" --glob "**/Domain/**/*.php"
# Immutability violations
Grep: "public function set[A-Z]" --glob "**/Domain/**/*.php"
Grep: "class.*(?<!readonly)" --glob "**/ValueObject/**/*.php"
# Leaky abstractions
Grep: "Doctrine|Eloquent|PDO" --glob "**/Domain/**/*Interface.php"
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.
- 7d ago First seen · 144 lines · 60 tokens per session scan A 7cf5b2b5da58
principles-auditor is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 21d ago), licensed MIT. It adds 60 tokens to every session and 1,200 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-08-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.