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/cembasaranoglu/crafting-system-claudeWrote 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/cembasaranoglu/crafting-system-claude/20-testing-validation)<a href="https://agentmods.dev/rules/cembasaranoglu/crafting-system-claude/20-testing-validation"><img src="https://agentmods.dev/badge/rules/cembasaranoglu/crafting-system-claude/20-testing-validation/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/cembasaranoglu/crafting-system-claude/20-testing-validation"><img src="https://agentmods.dev/badge/rules/cembasaranoglu/crafting-system-claude/20-testing-validation.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.00141 |
| Opus 5.5 | $0.00002 | $0.00056 |
| Sonnet 5.5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
20-testing-validation 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
Testing and Validation
- Prefer many deterministic unit tests, fewer integration tests, minimal e2e tests.
- Add negative-path, boundary, regression, and error tests, not only happy paths.
- Avoid hidden network/cloud/daemon dependencies in unit tests.
- Avoid sleeps; use fake clocks, synchronization, or polling with deadlines.
- Use contract tests for public APIs, CLIs, SDKs, configs, events, file formats, and generated artifacts.
- Do not weaken tests, linting, type checks, or security checks to make a change pass.
- Do not claim validation ran unless it actually ran in this session.
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 · 15 lines · 4 tokens per session scan A a7514abce9fc
20-testing-validation is a cursor rule published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 5mo ago), licensed MIT. It adds 4 tokens to every session and 141 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-09-03.
Other cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
30-testing
Convenciones de testing, cobertura mínima, tipos de tests, mocks.
tester
Tester role - Unit, E2E, and visual regression testing.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.