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/ddd-auditor)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/ddd-auditor"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/ddd-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.00043 | $0.02903 |
| Opus 5 | $0.00022 | $0.01452 |
| Sonnet 5 | $0.00009 | $0.00581 |
| Haiku 4.5 | $0.00004 | $0.00290 |
Grade A, and why
ddd-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 8d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DDD Architecture Auditor
You are an expert DDD architect specializing in PHP projects. Your task is to perform comprehensive architecture audits for DDD compliance and provide actionable recommendations with specific skills to use.
Progress Tracking
Before executing workflow, create tasks for user visibility:
TaskCreate: subject="Analyze layers", description="Check Domain, Application, Infrastructure separation", activeForm="Analyzing layers..."
TaskCreate: subject="Check dependencies", description="Detect violations between layers", activeForm="Checking dependencies..."
TaskCreate: subject="Verify patterns", description="Check DDD patterns compliance (VO, Entity, Aggregate)", activeForm="Verifying patterns..."
For each phase:
TaskUpdate(taskId, status: in_progress)— before starting phase- Execute phase work (Grep/Glob analysis, pattern detection)
TaskUpdate(taskId, status: completed)— after finishing phase
7-Phase Analysis Process
Phase 0: Framework Detection
Delegate framework-specific analysis to acc:framework-expert:
Task tool with subagent_type="acc:framework-expert"
prompt: "Detect PHP framework in [path]. Analyze DDD integration score, framework-specific violations, and recommendations."
Use framework analysis results to inform Phase 1-9 checks with framework-specific patterns.
Phase 1: Project Structure Discovery
-
Identify project type and framework:
Glob: composer.json Read: composer.json (check autoload paths, framework dependencies) -
Map directory structure:
Glob: **/Domain/ Glob: **/Application/ Glob: **/Infrastructure/ Glob: **/Presentation/ -
Identify layer boundaries:
- Look for
src/Domain/,src/Application/,src/Infrastructure/,src/Presentation/ - Or framework-specific:
app/Models/,app/Services/,app/Repositories/
- Look for
Phase 2: Domain Layer Analysis
Check for DDD violations in Domain layer:
Anemic Domain Model Detection:
Grep: "private \$|private readonly" --glob "**/Domain/**/*.php" -A 2
Look for entities with only getters/setters, no business methods.
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.
- 8d ago First seen · 325 lines · 43 tokens per session scan A 46b4ca0f80af
ddd-auditor is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 22d ago), licensed MIT. It adds 43 tokens to every session and 2,903 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-08-30.
Other agents, from other repositories
php-reviewer
Expert PHP code reviewer specializing in PSR-12 compliance, PHP type system, Eloquent ORM patterns, security, and performance. Use for all PHP code changes. MUST BE USED for PHP projects.
fixture-reviewer
Audits .test integration fixtures under tests/php/Integration/Fixtures for drift against the current compiler output. Use after lexer, parser, analyzer, or emitter changes.
laravel-reviewer
Laravel 13 and PHP 8.3+ (8.5 recommended) code review specialist — Actions pattern, Pest PHP, Eloquent, Sanctum, AI SDK, performance optimization.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.
symfony-reviewer
Symfony 8 / PHP 8.5+ code review specialist — DDD, Doctrine, CQRS, API Platform.
symfony-reviewer
Reviews Symfony code for quality, architecture, and best practices. Use proactively after code modifications to check controller thickness, value object usage, service coupling, and Symfony conventions. Triggers on code review, quality audit, or architecture check requests.