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/jim-schilling/splurge-ai-rulesWrote 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/jim-schilling/splurge-ai-rules/testing-standards)<a href="https://agentmods.dev/rules/jim-schilling/splurge-ai-rules/testing-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/testing-standards/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/jim-schilling/splurge-ai-rules/testing-standards"><img src="https://agentmods.dev/badge/rules/jim-schilling/splurge-ai-rules/testing-standards.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.00004 | $0.00477 |
| Opus 5.5 | $0.00002 | $0.00191 |
| Sonnet 5.5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
testing-standards 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
- Follow BDD/TDD (Behavior/Test Driven Development) practices.
- Validate behavior of public APIs only.
- Prefer validation using actual data, interfaces, and objects
- Minimize use of mocks, except where appropriate.
- Mock at architectural boundaries (external systems, I/O) but prefer real objects/data for internal logic.
- Ensure tests are isolated and do not depend on external systems or state.
- Each code module must have at least one corresponding test module.
- Unit test shall target 85% code coverage for all public interfaces and methods.
- Combination of unit tests and integration tests shall target 95% code coverage for all public interfaces and methods.
- Prefer tests that are independent, repeatable, and deterministic.
- Prefer shared helpers for common logic.
- Avoid validation of implementation details and private APIs.
- Prefer validation of patterns of text, and avoid exact matching of content and formatting.
- Prefer pytest; pytest-xdist may be used optionally for parallel runs (e.g., -n 4) when desired.
- Prefer pytest-cov for code coverage with parameters --cov=your_package --cov-report=term-missing.
- Prefer pytest-mock for mocking and patching, where appropriate.
- Run pytest with code coverage when asked by user, otherwise skip.
- Place unit tests in tests/unit/ and integration tests in tests/integration/, e2e tests in tests/e2e/, and performance tests in tests/performance/.
- Place test data in tests/data.
- For Python, prefer pure pytest function style tests.
- For Python, prefer use of tmp_path and tmp_path_factory fixtures for temporary files and directories.
- Name test methods as test_[condition]_[expectedResult].
- Each test method should ideally test a single condition and expected result.
- Use fixtures for common setup and teardown logic.
- Use parameterized tests for testing multiple input scenarios.
- Use assertions to validate expected outcomes.
- Prefer tests/unit/* to run to completion within 60 seconds.
- Prefer tests/integration/* to run to completion within 60 seconds.
- Prefer tests/e2e/* to run to run to completion within 60 seconds.
- Prefer tests/performance/* to run to completion within 60 seconds.
- Prefer entire test suite to run to completion within 120 seconds.
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 · 36 lines · 4 tokens per session scan A 27ee85143aad
testing-standards is a cursor rule published in the GitHub repository jim-schilling/splurge-ai-rules (3 stars, last pushed 1y ago), licensed MIT. It adds 4 tokens to every session and 477 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-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.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.