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.
npx skills add Tyler-R-Kendrick/agent-skills --skill domain-driven-designgit clone --depth 1 https://github.com/Tyler-R-Kendrick/agent-skillsWrote 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/skills/tyler-r-kendrick/agent-skills/domain-driven-design)<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/domain-driven-design"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/domain-driven-design/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/skills/tyler-r-kendrick/agent-skills/domain-driven-design"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/domain-driven-design.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.00107 | $0.03383 |
| Opus 5.5 | $0.00043 | $0.01353 |
| Sonnet 5.5 | $0.00021 | $0.00677 |
| Haiku 4.5 | $0.00011 | $0.00338 |
Grade A, and why
domain-driven-design 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 2mo 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain-Driven Design (DDD)
Overview
Domain-Driven Design is a software design approach that centers the development process on the core business domain. It provides both strategic patterns for organizing large systems and tactical patterns for modeling individual domains. DDD is especially valuable for complex domains where the business logic is the primary source of difficulty.
The canonical reference is Eric Evans' Domain-Driven Design: Tackling Complexity in the Heart of Software (2003), supplemented by Vaughn Vernon's Implementing Domain-Driven Design (2013) and Domain-Driven Design Distilled (2016).
Core premise: The structure of the software should mirror the structure of the business domain. The language used by developers should be the same language used by domain experts.
Strategic DDD
Strategic DDD deals with the big picture: how to decompose a large system into manageable parts, how those parts relate to each other, and how teams communicate across boundaries.
Ubiquitous Language
A shared, precise language between developers and domain experts for each bounded context. The same term means the same thing everywhere within a context -- in conversations, documentation, code, and tests.
Rules:
- One bounded context, one ubiquitous language.
- If a term means different things to different people, you likely have multiple bounded contexts.
- The language should appear literally in the code: class names, method names, variable names.
- Refine the language continuously as understanding deepens.
Example: In an e-commerce system, "Order" means different things in different contexts:
- Sales context: An Order is a customer's purchase intent with line items and pricing.
- Fulfillment context: An Order is a set of items to pick, pack, and ship.
- Billing context: An Order is an invoice with payment terms.
Each context has its own Order model with its own ubiquitous language.
Bounded Contexts
A bounded context is an explicit boundary within which a domain model is defined and applicable. Inside a bounded context, the ubiquitous language is consistent. Across bounded contexts, the same word may mean different things.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 16 KB
- metadata.json 754 B
- README.md 695 B
- rules/_sections.md 1.9 KB
- rules/_template.md 379 B
- rules/domain-driven-design-apply-ddd-only-where-the-domain-complexity-justifies-it.md 450 B
- rules/domain-driven-design-bounded-context-boundaries-often-align-well-with.md 525 B
- rules/domain-driven-design-collaborate-with-domain-experts-continuously-ddd-is-not.md 403 B
- rules/domain-driven-design-draw-context-maps-early-and-revisit-them-as-the-system.md 373 B
- rules/domain-driven-design-invest-heavily-in-ubiquitous-language.md 385 B
- rules/domain-driven-design-keep-aggregates-small.md 386 B
- rules/domain-driven-design-reference-other-aggregates-by-identity-never-by-direct.md 403 B
- rules/domain-driven-design-use-domain-events-for-cross-aggregate-and-cross-context.md 382 B
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.
- 2mo ago First seen · 326 lines · 107 tokens per session scan A b7edac7a7fc9
domain-driven-design is a skill published in the GitHub repository Tyler-R-Kendrick/agent-skills (13 stars, last pushed 5mo ago), licensed MIT. It adds 107 tokens to every session and 3,383 once invoked, about $0.0004 per session on Opus 5.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-31.
domain-driven-design compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| domain-driven-designTyler-R-Kendrick/agent-skills | Skill | 13 | 5mo ago | MIT | A | 107 | Claude Code |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 68k | 2d ago | Apache-2.0 | A | 217 | Claude Code, Codex |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 78 | Claude Code |
| fastapi-router-pymicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 46 | Claude Code |
| dev-runtimelangwatch/langwatch | Skill | 5.0k | yesterday | Apache-2.0 | A | 172 | Claude Code |
| api-designericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | A | 105 | Claude Code, Codex |
| migrate-segw-to-raparc-mcp/arc-1 | Skill | 252 | yesterday | MIT | A | 106 | Claude Code |