domain-driven-design

domain-driven-design is a skill for Claude Code, Codex from G1Joshi/Agent-Skills. It costs 15 tokens per session (747 once invoked), scanned A, original, MIT.

A set of Domain-Driven Design patterns for shaping software around a business area and the people who understand it. It covers strategic boundaries and tactical building blocks such as aggregate roots and domain events.

In plain words
What is it for?
Modeling complex systems such as insurance, banking, or logistics, defining service boundaries, and implementing business objects whose behavior enforces domain rules.
Why use it?
It helps developers manage complicated business rules and improve communication with domain experts. It can also guide the separation of a large monolithic application into smaller services.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Modeling complex systems such as insurance, banking, or logistics, defining service boundaries, and implementing business objects whose behavior enforces domain rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/g1joshi/agent-skills/domain-driven-design
Install

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.

Any agent
npx skills add G1Joshi/Agent-Skills --skill domain-driven-design
Clone the repo
git clone --depth 1 https://github.com/G1Joshi/Agent-Skills

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

agentmods 80×15 button for domain-driven-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/g1joshi/agent-skills/domain-driven-design"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/domain-driven-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 747 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 original No closer match found 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.00015 $0.00747
Opus 5 $0.00008 $0.00374
Sonnet 5 $0.00003 $0.00149
Haiku 4.5 $0.00002 $0.00075

Measured 9d ago against content hash c0134fe87bdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 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.

skills/architecture/domain-driven-design/SKILL.md · 96 lines

How it starts

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

Domain-Driven Design (DDD)

DDD is a software design approach focusing on modeling software to match a domain according to input from that domain's experts. It is essential for tackling high complexity in the heart of software.

When to Use

  • Complex business domains (e.g., Insurance, Banking, Logistics) where logic is intricate.
  • When there is a communication gap between developers and business experts.
  • decomposing a Monolith into Microservices (defining boundaries).

Quick Start

// Aggregate Root
public class Order {
    private OrderId id;
    private Money totalAmount;
    private OrderStatus status;
    private List<OrderItem> items; // Aggregates items

    // Behaviors (Rich Model), not just Getters/Setters
    public void addItem(Product product, int quantity) {
        if (this.status != OrderStatus.DRAFT) {
            throw new DomainException("Cannot modify confirmed order");
        }
        this.items.add(new OrderItem(product, quantity));
        recalculateTotal();
    }

    public void confirm() {
        if (items.isEmpty()) throw new DomainException("Order empty");
        this.status = OrderStatus.CONFIRMED;
        // Raise Domain Event
        DomainEvents.publish(new OrderConfirmed(this.id));
    }
}

Core Concepts

Ubiquitous Language

A common, rigorous language shared by developers and domain experts. If the expert calls it a "Policy", the code must call it Policy, not UserPlan or Subscription.

Bounded Context

The specific boundary within which a particular domain model is defined and applicable. Ideally maps to a Microservice or a Module.

Aggregates

A cluster of associated objects treated as a unit for data changes. External objects can only hold references to the Aggregate Root.

Common Patterns

Value Objects

Immutable objects defined by their attributes, not identity (e.g., Money, Address, Email). Two Money(5) objects are equal.

Domain Events

Something that happened in the domain that domain experts care about (OrderShipped, AccountDebited). Used to decouple side effects.

Read the full file on GitHub · 96 lines

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. 9d ago First seen · 96 lines · 15 tokens per session scan A c0134fe87bdb

Subscribe to this mod's changes

domain-driven-design is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 747 once invoked, about $0.0001 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.