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/krivoox/agent-stack-templateWrote 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/krivoox/agent-stack-template/tdd-domain)<a href="https://agentmods.dev/rules/krivoox/agent-stack-template/tdd-domain"><img src="https://agentmods.dev/badge/rules/krivoox/agent-stack-template/tdd-domain/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/krivoox/agent-stack-template/tdd-domain"><img src="https://agentmods.dev/badge/rules/krivoox/agent-stack-template/tdd-domain.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.00000 | $0.00281 |
| Opus 5.5 | $0.00000 | $0.00112 |
| Sonnet 5.5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
tdd-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 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
TDD — business logic
Red → green → refactor. The test comes first, and it must fail for the right reason before you write the implementation.
Tested
src/domain/**src/features/*/domain/**- Any pure calculation or invariant
Not tested
React components, styles, layout, snapshots. A snapshot test of a component is a maintenance cost with no signal — do not add one, even "for coverage".
Writing the test
- One behaviour per
it, named as the rule it protects, not as the function it calls:"rejects a duplicate name regardless of casing", not"works". - Assert on the error type from
src/domain/errors.ts, not on the message — copy changes, semantics do not. - Cover the boundary, not just the happy path: empty input, the limit itself, one past the limit, and the case that must be rejected.
- No mocks. If a rule needs the clock, a random value or a database row, that input is a parameter — this is what keeps the domain testable.
Full workflow
docs/tdd-workflow.md.
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 · 37 lines · 0 tokens per session scan A 53e481160794
tdd-domain is a cursor rule published in the GitHub repository krivoox/agent-stack-template (31 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 281 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-30.
Other cursor rules, from other repositories
tdd-skill
Before implementing or correcting production behavior, read and apply .agents/skills/tdd/SKILL.md. Also load it for behavior-preserving refactoring or when reviewing claimed TDD evidence, so its scope and exceptions are respected.
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
react-query-tests
// ✅ CORRECT: Legacy React Query pattern const ctx = konn() .beforeEach(() => createAppRouter()) .afterEach((ctx) => ctx?.close?.()) .done().
tanstack-react-query-tests
// ✅ CORRECT: Use await using for automatic cleanup await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
test-patterns
// ✅ CORRECT: Use await using for automatic cleanup await using ctx = testServerAndClientResource(router, { client(opts) { return { links: [ httpLink({ url: opts.httpUrl, fetch: mockFetch, }), ], }; }, }).
test-intent-readability
Tests must be readable by context (BDD-style grouping).