ropey: Skill for Claude Code

.agents/skills/domain-driven-design/SKILL.md

domain-driven-design is a skill for Claude Code, Codex from andrewesweet/ropey. It costs 120 tokens per session (3,087 once invoked), scanned A, a copy of domain-driven-design, MIT.

A software-design framework that models code around the real business area it serves, such as banking, shipping, or healthcare.

In plain words
What is it for?
It helps define business concepts, group related rules into bounded contexts, design aggregates and domain events, and review how different parts of a system interact.
Why use it?
It reduces confusion when business rules are complex by giving developers and domain experts shared terms and clearer boundaries between parts of the system.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is andrewesweet/ropey's own configuration. It tells Claude Code and Codex how to work on ropey itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ropey configures →

Reuse

Borrowing it

Nothing to install: this file belongs to andrewesweet/ropey. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/andrewesweet/ropey/main/.agents/skills/domain-driven-design/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/andrewesweet/ropey

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for domain-driven-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/andrewesweet/ropey/domain-driven-design/github.svg)](https://agentmods.dev/skills/andrewesweet/ropey/domain-driven-design)
Your own site
<a href="https://agentmods.dev/skills/andrewesweet/ropey/domain-driven-design"><img src="https://agentmods.dev/badge/skills/andrewesweet/ropey/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.

agentmods 80×15 button for domain-driven-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/andrewesweet/ropey/domain-driven-design"><img src="https://agentmods.dev/badge/skills/andrewesweet/ropey/domain-driven-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 120 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,087 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00120 $0.03087
Opus 5.5 $0.00048 $0.01235
Sonnet 5.5 $0.00024 $0.00617
Haiku 4.5 $0.00012 $0.00309

Measured 2mo ago against content hash 204684a2d1bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

This is a copy

86% identical to domain-driven-design — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/domain-driven-design/SKILL.md · 204 lines

How it starts

The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Domain-Driven Design Framework

Framework for tackling software complexity by modeling code around the business domain. The greatest risk in software is not technical failure -- it is building a model that does not reflect how the business actually works.

Core Principle

The model is the code; the code is the model. Software should embody a deep, shared understanding of the business domain. When domain experts and developers speak the same language and that language is directly expressed in the codebase, complexity becomes manageable and the system evolves gracefully as the business changes.

Scoring

Goal: 10/10. Rate any domain model 0-10 against the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps. Report the current score and the specific improvements needed to reach 10/10.

Framework

1. Ubiquitous Language

Core concept: A shared, rigorous language between developers and domain experts, used consistently in conversation, documentation, and code. When the language changes, the code changes -- and awkward naming in code feeds back into refining the language.

Why it works: Ambiguity is the root cause of most modeling failures. When a developer says "order" and an expert means "purchase request," bugs are inevitable; a ubiquitous language forces every name in code to map to a concept the business recognizes and validates.

Key insights:

  • The language emerges from deep collaboration, not a glossary bolted on after the fact
  • If a concept is hard to name, the model is likely wrong -- naming difficulty is a design signal
  • Technical jargon (DataProcessor vs. ClaimAdjudicator) hides domain logic from the experts who could correct it
  • Different bounded contexts may use the same word with different meanings -- and that is fine

Code applications:

Context Pattern Example
Class/method naming Name after domain concepts and verbs LoanApplication, policy.underwrite() -- not RequestHandler, process()
Module structure Organize by domain concept shipping/, billing/ -- not controllers/, services/
Code review Reject technical-only names Flag Manager, Helper, Processor, Utils as naming smells

Read the full file on GitHub · 204 lines

Files

What ships with it

6 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.

Changes

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.

  1. 2mo ago First seen · 204 lines · 120 tokens per session scan A 204684a2d1bc

Subscribe to this mod's changes

domain-driven-design is a skill published in the GitHub repository andrewesweet/ropey (0 stars, last pushed 4mo ago), licensed MIT. It adds 120 tokens to every session and 3,087 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to domain-driven-design, differing in 21 lines, and is treated as a copy.

Related

domain-driven-design compared with skills from other repositories

domain-driven-design next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
domain-driven-designandrewesweet/ropeySkill04mo agoMITA120Claude Code, Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code