V3 DDD Architecture

V3 DDD Architecture is a skill for Claude Code from shyftlabs/continuum. It costs 34 tokens per session (2,575 once invoked), scanned A, a copy of V3 DDD Architecture, Apache-2.0.

An architecture approach based on Domain-Driven Design, where software is divided into separate business areas with clear boundaries. It also applies clean architecture and modular design to claude-flow v3.

In plain words
What is it for?
Use it to identify domain boundaries, split responsibilities, design interfaces, and organize a modular TypeScript codebase.
Why use it?
It helps replace large, tangled modules with smaller parts that are easier to understand, test, and change independently.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to identify domain boundaries, split responsibilities, design interfaces, and organize a modular TypeScript codebase.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shyftlabs/continuum/v3-ddd-architecture
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 shyftlabs/continuum --skill v3-ddd-architecture
Clone the repo
git clone --depth 1 https://github.com/shyftlabs/continuum

Made for: Claude Code.

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 V3 DDD Architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/shyftlabs/continuum/v3-ddd-architecture/github.svg)](https://agentmods.dev/skills/shyftlabs/continuum/v3-ddd-architecture)
Your own site
<a href="https://agentmods.dev/skills/shyftlabs/continuum/v3-ddd-architecture"><img src="https://agentmods.dev/badge/skills/shyftlabs/continuum/v3-ddd-architecture/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 V3 DDD Architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/shyftlabs/continuum/v3-ddd-architecture"><img src="https://agentmods.dev/badge/skills/shyftlabs/continuum/v3-ddd-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,575 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 100% 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.00034 $0.02575
Opus 5 $0.00017 $0.01288
Sonnet 5 $0.00007 $0.00515
Haiku 4.5 $0.00003 $0.00258

Measured 5d ago against content hash da84eb1ab349, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

V3 DDD Architecture 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 5d 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

100% identical to V3 DDD Architecture — 0 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.

.claude/skills/v3-ddd-architecture/SKILL.md · 442 lines

How it starts

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

V3 DDD Architecture

What This Skill Does

Designs and implements Domain-Driven Design (DDD) architecture for claude-flow v3, decomposing god objects into bounded contexts, implementing clean architecture patterns, and enabling modular, testable code structure.

Quick Start

# Initialize DDD architecture analysis
Task("Architecture analysis", "Analyze current architecture and design DDD boundaries", "core-architect")

# Domain modeling (parallel)
Task("Domain decomposition", "Break down orchestrator god object into domains", "core-architect")
Task("Context mapping", "Map bounded contexts and relationships", "core-architect")
Task("Interface design", "Design clean domain interfaces", "core-architect")

DDD Implementation Strategy

Current Architecture Analysis

├── PROBLEMATIC: core/orchestrator.ts (1,440 lines - GOD OBJECT)
│   ├── Task management responsibilities
│   ├── Session management responsibilities
│   ├── Health monitoring responsibilities
│   ├── Lifecycle management responsibilities
│   └── Event coordination responsibilities
│
└── TARGET: Modular DDD Architecture
    ├── core/domains/
    │   ├── task-management/
    │   ├── session-management/
    │   ├── health-monitoring/
    │   ├── lifecycle-management/
    │   └── event-coordination/
    └── core/shared/
        ├── interfaces/
        ├── value-objects/
        └── domain-events/

Domain Boundaries

1. Task Management Domain
// core/domains/task-management/
interface TaskManagementDomain {
  // Entities
  Task: TaskEntity;
  TaskQueue: TaskQueueEntity;

  // Value Objects
  TaskId: TaskIdVO;
  TaskStatus: TaskStatusVO;
  Priority: PriorityVO;

  // Services
  TaskScheduler: TaskSchedulingService;
  TaskValidator: TaskValidationService;

  // Repository
  TaskRepository: ITaskRepository;
}
2. Session Management Domain
// core/domains/session-management/
interface SessionManagementDomain {
  // Entities
  Session: SessionEntity;
  SessionState: SessionStateEntity;

  // Value Objects
  SessionId: SessionIdVO;
  SessionStatus: SessionStatusVO;

  // Services
  SessionLifecycle: SessionLifecycleService;
  SessionPersistence: SessionPersistenceService;

  // Repository
  SessionRepository: ISessionRepository;
}

Read the full file on GitHub · 442 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. 5d ago First seen · 442 lines · 34 tokens per session scan A da84eb1ab349

Subscribe to this mod's changes

V3 DDD Architecture is a skill published in the GitHub repository shyftlabs/continuum (84 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,575 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to V3 DDD Architecture, differing in 0 lines, and is treated as a copy.