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/c9r-io/orchestrator/testing-conventionsgit clone --depth 1 https://github.com/c9r-io/orchestratorWhat 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.00294 | $0.00294 |
| Opus 5 | $0.00147 | $0.00147 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
testing-conventions 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 Conventions
TDD Loop (Preferred)
- RED: write a failing test for the next behavior.
- GREEN: implement the smallest change to pass.
- REFACTOR: improve design while keeping tests green.
Test Pyramid (Platform Guidance)
- Unit tests: most of the coverage; fast; no Docker.
- Integration tests: limited; validate boundaries (DB, external APIs) when needed.
- E2E tests: few; validate critical user journeys.
- Performance tests: targeted benchmarks for latency/throughput regressions.
Practical Rules
- Every feature plan must include: test plan + acceptance criteria.
- After implementation, generate QA docs under
docs/qa/and treat them as the reproducible acceptance spec. - Failures discovered in QA become tickets under
docs/ticket/with steps + evidence + expected/actual.
Coverage Targets (Guidance, Not Law)
- Aim for high coverage in business logic (80%+).
- Prefer meaningful assertions over chasing percentages.
Suggested Commands (Project-Specific)
The exact commands depend on the generated project. Common patterns:
# Unit tests
cargo test
npm test
# Coverage (if configured)
cargo llvm-cov --html
npm run test -- --coverage
# E2E (if configured)
npx playwright test
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 · 49 lines · 294 tokens per session scan A c3f16418e9d8
testing-conventions is a cursor rule published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 7d ago), licensed MIT. It adds 294 tokens to every session, about $0.0015 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-30.
Other cursor rules, from other repositories
incremental-verify
Verify each behavior before building the next. One test, one implementation, one commit. No bulk-writing tests for behavior that does not yet exist.
test_first_workflow
Enforce test-first or test-alongside development. Load when implementing new features, APIs, or UI components.
tdd
Test-driven development — red-green-refactor cycle.
tdd-required
Test-driven development required.
tester-rules
Rules for the Tester (TDD) mode.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.