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.
git clone --depth 1 https://github.com/BetterTyped/hype-stackWrote 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/bettertyped/hype-stack/domain-modeling)<a href="https://agentmods.dev/rules/bettertyped/hype-stack/domain-modeling"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/domain-modeling/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/rules/bettertyped/hype-stack/domain-modeling"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/domain-modeling.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00355 | $0.00355 |
| Opus 5.5 | $0.00142 | $0.00142 |
| Sonnet 5.5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
domain-modeling 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 1mo 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 Vocabulary and Decisions
Glossary (CONTEXT.md)
Canonical domain terms live in CONTEXT.md at the repo root. Consistent vocabulary is what keeps schemas, routes, types, and UI copy coherent across sessions.
- Use glossary terms exactly — in code, schemas, route paths, DB tables, and messages. Do not invent synonyms (
accountvsuservsmember,cancelvsrevoke— pick the canonical one). - When you introduce a new domain concept, add it to
CONTEXT.mdin the same change: one line, term + definition. - When the user's wording conflicts with the glossary, point out the conflict and ask which term wins — then update the glossary if it changes.
- If
CONTEXT.mddoes not exist yet, create it the first time a domain term needs pinning down.
Architecture Decision Records (docs/adr/)
Significant architectural decisions get a short ADR in docs/adr/NNNN-<slug>.md: context, decision, consequences — a few paragraphs, not an essay.
- Read existing ADRs before proposing structural changes in the area you're touching.
- Do not re-litigate recorded decisions. If a decision looks wrong, say so and ask — never silently refactor around it.
- Record a new ADR when a decision is hard to reverse, cross-cutting, or the kind of thing a future session would otherwise "helpfully" undo (library choice, data model shape, seam placement).
- Create
docs/adr/lazily, when the first ADR is needed.
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.
- 1mo ago First seen · 25 lines · 355 tokens per session scan A 998455bbac7d
domain-modeling is a cursor rule published in the GitHub repository BetterTyped/hype-stack (12 stars, last pushed 15d ago), licensed MIT. It adds 355 tokens to every session, about $0.0014 per session on Opus 5.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-31.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.
project-structure
Folder layout for Next.js App Router and Vite + React variants.