04-tdd-mandatory

A test-first development rule, often called TDD, where a failing test is written before changing behavior.

In plain words
What is it for?
It is for guiding behavior changes, bug fixes, integration tests, end-to-end tests, and checks that the application context starts correctly.
Why use it?
It provides evidence that the new behavior works and that bug fixes remain protected by regression tests, including tests that start the full application when required.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/joaonic/agentkit/04-tdd-mandatory
Clone the repo
git clone --depth 1 https://github.com/Joaonic/agentkit
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00164
Opus 5 $0.00000 $0.00082
Sonnet 5 $0.00000 $0.00033
Haiku 4.5 $0.00000 $0.00016

Measured yesterday against content hash cab081c0f8ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

04-tdd-mandatory 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 yesterday.

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.

src/core/rules/04-tdd-mandatory.mdc · 18 lines

What it actually says

TDD Mandatory

Mandatory:

  • failing test before behavior change
  • regression test for bug fixes
  • deterministic and meaningful assertions
  • integration/E2E tests MUST boot full application context (@SpringBootTest without classes=) with Testcontainers
  • @Import and @ContextConfiguration(classes=...) are ONLY for slice tests (@WebMvcTest, @DataJpaTest) — NEVER for integration/E2E
  • if application context fails to start, fix the application — never fix the test to skip context loading

No merge-ready status for behavior changes without test evidence.

Changes

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.

  1. yesterday First seen · 18 lines · 0 tokens per session scan A cab081c0f8ea

Subscribe to this mod's changes

04-tdd-mandatory is a cursor rule published in the GitHub repository Joaonic/agentkit (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 164 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.