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/secondlifes/delphi-expert/tdd-patternsgit clone --depth 1 https://github.com/SecondLifes/delphi-expertWrote 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/secondlifes/delphi-expert/tdd-patterns)<a href="https://agentmods.dev/rules/secondlifes/delphi-expert/tdd-patterns"><img src="https://agentmods.dev/badge/rules/secondlifes/delphi-expert/tdd-patterns.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.00285 | $0.00285 |
| Opus 5 | $0.00143 | $0.00143 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
tdd-patterns 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.
What it actually says
Delphi TDD and Unit Tests (DUnitX)
- Test-First (Red-Green-Refactor): When implementing new rules under "TDD" order, you MUST first structure the Test Case and its failed assertions (
Assert), before designing the concrete business logic algorithms. - Expressive Standard Nomenclature: Test method prefixes must follow the
Metodo_Cenario_Expectativasemantic scope. Example:[Test] procedure CalculateTax_EmptyOrder_ThrowsException;. - Default Framework: Use
DUnitX. Always decorate test classes with[TestFixture], methods with[Test]and setups with[Setup] / [TearDown]. - Total Isolation (Fakes/Mocks): NEVER write a unit test that involves direct coupling with the
TFDConnectionDatabase, external APIs, Network or VCL/Forms. Everything external to the tested Service or Entity must be simulated in the test file in a FAKE isolated subclass implementing the Dependency Interface (IMyRepository). - Exception Validation: To prove domain Guard Clauses, instantiate anonymous methods using
Assert.WillRaise()by injecting the expected type ofException.
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 · 13 lines · 285 tokens per session scan A 7cdcf06e7158
tdd-patterns is a cursor rule published in the GitHub repository SecondLifes/delphi-expert (3 stars, last pushed 2d ago), licensed MIT. It adds 285 tokens to every session, about $0.0014 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
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.