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.
npx agentmods add rules/aiagentwithdhruv/ai-dev-stack/80-testing-qualitygit clone --depth 1 https://github.com/aiagentwithdhruv/ai-dev-stackWhat 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 | $0.00194 | $0.00194 |
| Opus 5 | $0.00097 | $0.00097 |
| Sonnet 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 2d 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.
- 2d 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 (10 stars, last pushed 2mo ago), licensed MIT. It adds 194 tokens to every session, about $0.0010 per session on Opus 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
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
cursorrules
Code exhibits taste — Torvalds' term for finding the formulation where special cases disappear. Seek representations where edge cases become impossible, the type system proves correctness, and the API guides users into the pit of success.
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.