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/Arenukvern/mcp_flutterWrote 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/arenukvern/mcp_flutter/test_use_tdd)<a href="https://agentmods.dev/rules/arenukvern/mcp_flutter/test_use_tdd"><img src="https://agentmods.dev/badge/rules/arenukvern/mcp_flutter/test_use_tdd/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/arenukvern/mcp_flutter/test_use_tdd"><img src="https://agentmods.dev/badge/rules/arenukvern/mcp_flutter/test_use_tdd.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.00009 | $0.00092 |
| Opus 5.5 | $0.00004 | $0.00037 |
| Sonnet 5.5 | $0.00002 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
test_use_tdd 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
Always use TDD writing code. One exception - examples folder. MEANING: describe behaviour in test, then fix implementation. The test can fail (if real implementaion is broken) and this way we could develop healthy software. While writing test always use Ruby philosophy - red -> green. Meaning: we express meaning through the tests and then implement them.
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 · 10 lines · 9 tokens per session scan A 87b4ebeffe42
test_use_tdd is a cursor rule published in the GitHub repository Arenukvern/mcp_flutter (392 stars, last pushed 8d ago), licensed MIT. It adds 9 tokens to every session and 92 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
workflow
BDD delivery order, Gherkin spec before tests before code, definition of done, Rules Sync.
gwt-tests
Title: Given/When/Then test convention.
validation-harness
Validation harness — interfaces, adapters, cenários E2E.
testing
Cursor rule "testing" from BlackLeg15/desafio_bloc_1, covering testing and cobertura existente.
typescript
You are an expert in building MCP servers in TypeScript using a test-driven design methodology.
test-driven-development
Your Role and Mission: You are an expert TDD Software Developer AI specializing in Python. Your primary function is to write Python code by strictly adhering to the Test-Driven Development (TDD) methodology using the pytest framework. Your goal is to produce high-quality, robust, maintainable, and well-documented…