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/solvapay/solvapay-sdkWrote 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/solvapay/solvapay-sdk/tdd)<a href="https://agentmods.dev/rules/solvapay/solvapay-sdk/tdd"><img src="https://agentmods.dev/badge/rules/solvapay/solvapay-sdk/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/solvapay/solvapay-sdk/tdd"><img src="https://agentmods.dev/badge/rules/solvapay/solvapay-sdk/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.00017 | $0.00350 |
| Opus 5.5 | $0.00007 | $0.00140 |
| Sonnet 5.5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
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
Test-Driven Development
Use RED-GREEN-REFACTOR for all bug fixes and new features.
Workflow
- RED -- Write a failing test that describes the expected behavior
- GREEN -- Write the minimal code to make the test pass
- REFACTOR -- Clean up the implementation while keeping tests green
Bug Fixes
Always write a test that reproduces the bug before writing the fix:
- Write a test that fails because of the bug
- Run the test to confirm it fails
- Fix the bug with minimal changes
- Run the test again to confirm it passes
- Refactor if needed
New Features
Write tests for the expected behavior before implementing:
- Define the expected inputs and outputs
- Write tests covering the happy path and key edge cases
- Implement until all tests pass
- Refactor the implementation
Test Structure
- Co-locate tests:
*.test.tsnext to the source file - One behavior per test: each
it()should test a single expectation - Descriptive names:
it('should throw when API key is missing') - Arrange-Act-Assert: set up data, call the function, check the result
Running Tests
npx vitest run <path>-- run a single test filenpx vitest --watch-- run tests in watch modenpx vitest run-- run all tests
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 · 47 lines · 17 tokens per session scan A 4b9dbe6c293f
tdd is a cursor rule published in the GitHub repository solvapay/solvapay-sdk (5 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 350 once invoked, about $0.0001 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
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
common-testing
Testing requirements: 80% coverage, TDD workflow.
testing_rules
A testing guide covering TDD, where tests are written before code, and BDD, where expected behavior is described in Given-When-Then form.
tdd
Test-driven development — red-green-refactor cycle.
testing-standards
testing guidelines and expectations.