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 bdfinst/agentic-dev-team --skill domain-driven-designgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/domain-driven-design)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/domain-driven-design"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/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/bdfinst/agentic-dev-team/domain-driven-design"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/domain-driven-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.02136 |
| Opus 5.5 | $0.00017 | $0.00854 |
| Sonnet 5.5 | $0.00008 | $0.00427 |
| Haiku 4.5 | $0.00004 | $0.00214 |
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 1mo 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain-Driven Design (DDD)
Overview
Model software around the business domain. Collaborate with domain experts to build a shared understanding expressed in code through ubiquitous language, bounded contexts, and tactical patterns.
Strategic Patterns
Ubiquitous Language
- Code, documentation, and communication all use the same domain terminology
- If the domain expert calls it an "enrollment," the code calls it
Enrollment, notRegistration - Language inconsistencies signal a modeling problem
Bounded Contexts
- Each context owns its own domain model with clear boundaries
- The same real-world concept may have different representations in different contexts
- A
Customerin Billing is not the same model as aCustomerin Shipping
Context Mapping
Define explicit relationships between bounded contexts:
| Pattern | When to Use |
|---|---|
| Shared Kernel | Two contexts co-own a small, stable subset of the model |
| Anti-Corruption Layer | Protect your model from a messy or legacy external model |
| Customer/Supplier | Upstream context serves downstream; downstream can negotiate |
| Conformist | Downstream adopts upstream's model as-is (no negotiation power) |
| Open Host Service | Context exposes a well-defined protocol for many consumers |
| Published Language | Shared interchange format (e.g., industry standard schemas) |
| Separate Ways | No integration at all — the cheaper, more honest choice when the cost of integrating two contexts outweighs the benefit |
Distillation — Find the Core Domain
Not all of the model is equally valuable. Spend your best modeling effort where it earns the most.
- Core Domain — the part that makes the business worth doing; your competitive advantage. Assign your strongest people here; invest in supple design.
- Generic Subdomains — necessary but undifferentiated (auth, notifications, currency conversion). Buy, adopt, or build plainly — do not gold-plate.
- Supporting Subdomains — business-specific but not differentiating. Build simply.
- Domain Vision Statement — a short paragraph naming the Core Domain and why it matters. Write it early; it directs investment and prioritization.
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.
- 1mo ago First seen · 195 lines · 42 tokens per session scan A d10903b2450f
domain-driven-design is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 2,136 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…