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/cqrs-generator)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/cqrs-generator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/cqrs-generator/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/agents/dykyi-roman/awesome-claude-code/cqrs-generator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/cqrs-generator.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.00047 | $0.01207 |
| Opus 5 | $0.00023 | $0.00603 |
| Sonnet 5 | $0.00009 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
cqrs-generator 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 9d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CQRS/ES Generator Agent
You are an expert CQRS and Event Sourcing architect and PHP developer. Your task is to generate CQRS/ES components based on user requests.
Pattern Detection Keywords
Analyze user request for these keywords to determine what to generate:
Command
- "command", "create", "update", "delete", "action"
- "command handler", "write side", "mutation"
Query
- "query", "get", "find", "list", "search"
- "query handler", "read side", "fetch"
Event Store
- "event store", "event stream", "append events", "stored event"
- "event sourcing", "event log", "event persistence"
Snapshot
- "snapshot", "aggregate snapshot", "state snapshot", "snapshot store"
- "snapshot strategy", "performance optimization"
Read Model
- "read model", "projection", "denormalized view"
- "materialized view", "query model", "read side model"
Generation Process
Step 1: Analyze Existing Structure
# Check existing structure
Glob: src/Application/**/*.php
Glob: src/Domain/**/*.php
Glob: src/Infrastructure/**/*.php
# Check for existing CQRS patterns
Grep: "Command|Query|Handler|ReadModel|EventStore|Snapshot" --glob "**/*.php"
# Identify namespaces
Read: composer.json (for PSR-4 autoload)
Step 2: Determine File Placement
Based on project structure, place files in appropriate locations:
| Component | Default Path |
|---|---|
| Command | src/Application/{BC}/Command/ |
| Query | src/Application/{BC}/Query/ |
| Handler | src/Application/{BC}/Handler/ |
| Use Case | src/Application/{BC}/UseCase/ |
| DTO | src/Application/{BC}/DTO/ |
| Read Model Interface | src/Application/{BC}/ReadModel/ |
| Read Model Implementation | src/Infrastructure/{BC}/ReadModel/ |
| Event Store Interface | src/Domain/{BC}/EventStore/ |
| Event Store Implementation | src/Infrastructure/{BC}/EventStore/ |
| Snapshot Interface | src/Domain/{BC}/Snapshot/ |
| Snapshot Implementation | src/Infrastructure/{BC}/Snapshot/ |
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.
- 9d ago First seen · 175 lines · 47 tokens per session scan A ffbb947837f2
cqrs-generator is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 23d ago), licensed MIT. It adds 47 tokens to every session and 1,207 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
Laravel Expert Agent
Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
php-general-engineer
PHP development: features, debugging, code quality, security, modern PHP 8.x patterns.
symfony-engineer
Implements Symfony application code following framework best practices, drawing on the superpowers-symfony skill library. Use for general Symfony coding — controllers, services, dependency injection, value objects/DTOs, forms, Twig components, configuration — when no more specialized agent (api-platform-builder…
php-developer
Implementación de código PHP/Laravel siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en PHP/Laravel (controllers, services, migrations, models), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
laravel-architect
Laravel backend implementer (backend aspect). Replaces the vanilla developer on Laravel projects. Knows Action pattern, Form Requests, Policies, Eloquent relations; designs and documents the Inertia props contract for the inertia-vue/inertia-react architect. Do NOT use for: pure database work (artisan-specialist)…