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/danielvm-git/bigpowers/model-domaingit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/model-domain)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/model-domain"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/model-domain.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00057 | $0.02398 |
| Opus 5 | $0.00028 | $0.01199 |
| Sonnet 5 | $0.00011 | $0.00480 |
| Haiku 4.5 | $0.00006 | $0.00240 |
Grade A, and why
model-domain 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 today.
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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model Domain
Distinct from define-language and deepen-architecture: Use this skill to stress-test a plan through a grilling interview that resolves domain model decisions and captures invariants. Use define-language to produce a canonical glossary of terms. Use deepen-architecture to find module-level refactoring opportunities in code.
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
HARD GATE — Capture invariants (what MUST always be true) and state machines (what transitions are legal) for core entities. If these are fuzzy, design will fail.
Ask the questions one at a time, waiting for feedback on each question before continuing.
If a question can be answered by exploring the codebase, explore the codebase instead.
Domain awareness
During codebase exploration, also look for existing documentation:
File structure
Most repos have a single context:
/
├── specs/
│ ├── CONTEXT.md
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
If a specs/tech-architecture/tech-stack.md exists, the repo has multiple contexts. The map points to where each one lives:
/
├── specs/
│ ├── CONTEXT-MAP.md
│ └── adr/ ← system-wide decisions
└── src/
├── ordering/
│ └── specs/
│ ├── CONTEXT.md
│ └── adr/ ← context-specific decisions
└── billing/
└── specs/
├── CONTEXT.md
└── adr/
Create files lazily — only when you have something to write. If no specs/tech-architecture/tech-stack.md exists, create it when the first term is resolved. If no specs/adr/ exists, create it when the first ADR is needed.
During the session
Challenge against the glossary
When the user uses a term that conflicts with the existing language in specs/tech-architecture/tech-stack.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"
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.
- today First seen · 232 lines · 57 tokens per session scan A 3c89bfe1887b
model-domain is a cursor rule published in the GitHub repository danielvm-git/bigpowers (162 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 2,398 once invoked, about $0.0003 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 cursor rules, from other repositories
data-science
Rules for data science, ML, and Jupyter notebook work.
ai-interview-skills
AI外呼Prompt工程化工具包 - 提供生成Prompt、生成输入变量、评估通话质量三个技能.
50-rag-system
Retrieval-augmented generation rules.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
ai-assisted-development
AI-Assisted Development: prompt structure, context management, iterative refinement.