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/generate-ddd)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/generate-ddd"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/generate-ddd.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.00046 | $0.01158 |
| Opus 5 | $0.00023 | $0.00579 |
| Sonnet 5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
generate-ddd 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 4d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate DDD Components
Generate Domain-Driven Design components for PHP 8.4 with tests and proper layer placement.
Input Parsing
Parse $ARGUMENTS to extract component type, name, and optional meta-instructions:
Format: <component-type> <ComponentName> [-- <meta-instructions>]
Examples:
- /acc:generate-ddd entity Order
- /acc:generate-ddd vo Email
- /acc:generate-ddd aggregate Order -- with OrderLine child entity
- /acc:generate-ddd command CreateOrder
- /acc:generate-ddd query GetOrderById
Parsing rules:
- First part = component type (required, see list below)
- Second part = component name (required)
- After
--= meta-instructions (optional customizations)
Supported Components
Domain Layer Components
| Component | Aliases | Skill Used |
|---|---|---|
entity |
ent |
acc:create-entity |
value-object |
vo, valueobject |
acc:create-value-object |
aggregate |
agg, aggregate-root |
acc:create-aggregate |
domain-event |
event, de |
acc:create-domain-event |
repository |
repo |
acc:create-repository |
domain-service |
service, ds |
acc:create-domain-service |
factory |
fact |
acc:create-factory |
specification |
spec |
acc:create-specification |
Application Layer Components
| Component | Aliases | Skill Used |
|---|---|---|
command |
cmd |
acc:create-command |
query |
qry |
acc:create-query |
use-case |
usecase, uc |
acc:create-use-case |
dto |
data-transfer |
acc:create-dto |
Event Sourcing Components
| Component | Aliases | Skill Used |
|---|---|---|
event-store |
es, eventstore |
acc:create-event-store |
snapshot |
snap |
acc:create-snapshot |
read-model |
rm, projection |
acc:create-read-model |
Integration Layer Components
| Component | Aliases | Skill Used |
|---|---|---|
acl |
anti-corruption |
acc:create-anti-corruption-layer |
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.
- 4d ago First seen · 139 lines · 46 tokens per session scan A 5508f14ca83a
generate-ddd is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 22d ago), licensed MIT. It adds 46 tokens to every session and 1,158 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
tests
Run the Week 4 backend test workflow. Build TESTARGS from $ARGUMENTS: use backend/tests when it is empty; prepend backend/tests when it starts with an option such as -k; otherwise use the supplied path or node ID as-is.
api-endpoint
Création Endpoint API Platform.
testing
Comprehensive testing setup for FastAPI applications with pytest and async support.
dare-laravel-api
Padrões DARE para APIs REST em Laravel 11 + PHP 8.3. Strict Types, FormRequests, Services, Resources, Repositories, Eloquent + casts, tratamento global de exceções, testes Pest, PHPStan/Larastan nível 8.
create
Scaffold a complete new Laravel package with Pest v4, Testbench v10, and Workbench.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.