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/aiagentwithdhruv/ai-dev-stackWrote 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/aiagentwithdhruv/ai-dev-stack/80-testing-quality)<a href="https://agentmods.dev/rules/aiagentwithdhruv/ai-dev-stack/80-testing-quality"><img src="https://agentmods.dev/badge/rules/aiagentwithdhruv/ai-dev-stack/80-testing-quality/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/aiagentwithdhruv/ai-dev-stack/80-testing-quality"><img src="https://agentmods.dev/badge/rules/aiagentwithdhruv/ai-dev-stack/80-testing-quality.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.00194 | $0.00194 |
| Opus 5.5 | $0.00078 | $0.00078 |
| Sonnet 5.5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
80-testing-quality 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 philosophy:
- Write production-quality code with tests for critical behavior.
- Prefer deterministic unit tests for business logic.
- Add integration tests for APIs, repositories, pipelines, and workflows crossing boundaries.
- Mock external services, cloud dependencies, and model providers where appropriate.
Testing expectations:
- Add tests for non-trivial service methods.
- Add tests for auth and permission-sensitive flows.
- Add tests for RAG/agent logic at the orchestration level where feasible.
- Cover validation, failure, and edge cases.
- Keep tests readable and isolated.
Code quality:
- Use linting and formatting.
- Use types wherever the stack supports them.
- Keep functions focused.
- Refactor repeated logic into shared utilities when justified.
Do not:
- Add major logic without at least basic tests.
- Create brittle tests tied to unstable implementation details.
- Depend on live external APIs in normal test flows.
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 · 29 lines · 194 tokens per session scan A 723dc7b25c38
80-testing-quality is a cursor rule published in the GitHub repository aiagentwithdhruv/ai-dev-stack (11 stars, last pushed 3mo ago), licensed MIT. It adds 194 tokens to every session, about $0.0008 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
jest
Jest: describe/it, matchers, mocking, async testing.
pytest
You are an expert in pytest testing. Follow these rules.
vitest
Vitest: unit testing, mocking, coverage, snapshot testing.
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
unity-testing
Unity Test Framework (Production Standards).
testing
Testing: test design, mocking strategy, coverage philosophy.