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 agentmods add rules/cmnemoi/cursor-rules/002-domain-driven-designgit clone --depth 1 https://github.com/cmnemoi/cursor-rulesWhat 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 | $0.00000 | $0.00387 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
002-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 2d 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.
What it actually says
Domain-Driven Design Standards
1.0.0
Context
- These rules apply to the modeling of business domains
- They ensure software accurately reflects business concepts and processes
- They promote a shared understanding between technical and domain experts
- Reflect business needs in the code.
- Avoid technical function names, favor domain language
Requirements
Ubiquitous Language
- Use consistent terminology across code, documentation, and communication
- Name classes, methods, and variables according to the domain language
- Document domain terms in a glossary
- Avoid technical jargon in domain models
Bounded Contexts
- Identify and define clear boundaries between different domain areas
- Create explicit context maps to document relationships between contexts
- Use different models for the same concept in different contexts when appropriate
- Implement proper integration patterns between bounded contexts
Domain Models
- Model entities with identity and continuity
- Model value objects for concepts defined by their attributes
- Implement aggregates to enforce consistency boundaries
- Use domain events to represent state changes
Business Rules
- Encapsulate business rules within domain entities and value objects
- Implement domain services for operations that don't belong to entities
- Use specifications to encapsulate complex query logic
- Validate business rules at the domain level
Architecture
- Implement a layered architecture with the domain model at the core
- Keep domain logic free from infrastructure concerns
- Use repositories to abstract data access
- Implement factories for complex object creation
Critical Rules
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.
- 2d ago First seen · 57 lines · 387 tokens per session scan A 6e03f7850c60
002-domain-driven-design is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 tokens. 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.