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 nWave-ai/nWave --skill nw-ddd-tacticalgit clone --depth 1 https://github.com/nWave-ai/nWaveWrote 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/nwave-ai/nwave/nw-ddd-tactical)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-ddd-tactical"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-ddd-tactical/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/nwave-ai/nwave/nw-ddd-tactical"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-ddd-tactical.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.00032 | $0.01420 |
| Opus 5 | $0.00016 | $0.00710 |
| Sonnet 5 | $0.00006 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
nw-ddd-tactical 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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tactical DDD
Implementation patterns within a bounded context. Tactical DDD answers: "How do we structure the domain model?"
Aggregates
An aggregate is a consistency boundary -- a cluster of domain objects that must be transactionally consistent.
Vernon's Four Design Rules
-
Model true invariants in consistency boundaries: Only include elements that MUST be consistent within the same transaction. If two entities don't share an invariant, they belong in separate aggregates.
-
Design small aggregates: ~70% of aggregates contain only a root entity with value-typed properties. Large aggregates create concurrency contention, scalability failures, and memory pressure.
-
Reference other aggregates by identity: Use
ProductIdnotProduct. Direct object references create accidental cross-aggregate transactions and prevent independent scaling. -
Use eventual consistency outside the boundary: Domain events communicate across aggregates. One transaction = one aggregate. If you need to update two aggregates "atomically," reconsider your boundaries.
Aggregate Design Checklist
- Contains only elements sharing true invariants
- Root entity controls all access (no direct child manipulation)
- External references by ID only (no object graphs)
- Small enough for single-transaction performance
- Command produces events (in event-sourced systems) or mutates state (in traditional)
- Business rules validated in command handling, not in persistence layer
Common Aggregate Smells
| Smell | Signal | Fix |
|---|---|---|
| God Aggregate | >5 entities, frequent concurrency conflicts | Split by invariant analysis |
| Anemic Aggregate | All logic in services, aggregate = data bag | Move business rules into aggregate methods |
| Cross-Aggregate Transaction | Two aggregates modified in one DB transaction | Use domain events + eventual consistency |
| Deep Nesting | Aggregate root -> entity -> entity -> value | Flatten; promote nested entities to own aggregates |
| Missing Aggregate | Business rules scattered in application services | Identify invariant cluster, create aggregate |
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.
- 6d ago First seen · 130 lines · 32 tokens per session scan A 7eb1a4b35848
nw-ddd-tactical is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 1,420 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
trivia-get-trivia
Returns a random trivia question with multiple-choice answers. Use the optional category and difficulty query parameters to filter the question pool.
RabbitAdvisors 知识付费案例研究
A step-by-step case study of building a paid knowledge product for a fictional company, RabbitTech. It demonstrates domain-driven design (DDD), an approach to shaping software around business concepts, and its use with microservices, separately deployable services.
限界上下文
A clear boundary around part of a business domain and its model. The same word can have different meanings inside different boundaries.
上下文映射
A way to describe how separate domain contexts relate to one another and integrate. It includes approaches such as a shared core or a translation layer that protects one model from another.
聚合 (Aggregate)
A group of related domain objects treated as one consistency boundary, with an aggregate root controlling access to the group. It defines which changes must be kept valid together.
DDD 与 MVC 对比
A comparison of Model-View-Controller (MVC), a common way to organize web applications, with Domain-Driven Design (DDD), a way to model complex business behavior. It explains where MVC may become insufficient as business rules grow.