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/dobryakov/cursor-rules/testing-rulesgit clone --depth 1 https://github.com/dobryakov/cursor-rulesWhat 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.00287 | $0.00287 |
| Opus 5 | $0.00143 | $0.00143 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
testing-rules 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 yesterday.
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 Strategy
- Do not run tests on the host! Run tests inside docker containers.
- After completing each task, run the relevant automated tests, including browser and performance tests whenever possible.
- Choose the environment according to the type of tests: put unit tests inside the service container, put API and e2e tests in separate test containers. Make sure to add the tests dir to the image.
- Connect test containers to the main
docker-compose.yml. - Before starting tests, check if the test container needs to be rebuilt and migrations applied.
- If the project includes an SDK or software clients, they must be covered by separate tests.
- If using Playwright, make sure you have browsers installed to the test container.
- If using Playwright, consider to use proper "FROM" image (for example, debian-based node.js image) in the Dockerfile before building test container.
- When calling
docker compose logswithtail, use proper syntax:docker compose logs --tail 10 <container name>. - It is recommended to include tests dir to the container as
volumesin docker-compose.yml to re-run the tests without re-building the image. - Always try first to debug the errors/warnings by running the corresponding tests. Add the tests if its needed.
- After fixing every bug, write tests to cover it, and run them.
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.
- yesterday First seen · 19 lines · 287 tokens per session scan A 2613318e5415
testing-rules is a cursor rule published in the GitHub repository dobryakov/cursor-rules (2 stars, last pushed 2mo ago), licensed MIT. It adds 287 tokens to every session, about $0.0014 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.