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/louisbrulenaudet/monorepo-template/testinggit clone --depth 1 https://github.com/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/testing)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/testing"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/testing.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
testing 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 Rules
Toolchain and Workers pool details: vitest.mdc, hono-workers.mdc. Front-app React/Query/Router Vitest: front-react.mdc.
- Put unit tests under the app or package at a
tests/directory that mirrors the source area. - Keep Vitest tests deterministic and avoid assertions that depend on test order.
- Test at the trust boundaries the app actually enforces today (shared Zod Mini schemas, constrained value sets, CORS/fail-closed responses, route status codes). Prefer asserting observable behavior over internals. Do not invent auth or idempotency tests for surfaces that do not exist yet.
anyis allowed only in*.test.ts/*.spec.ts(typescript/no-explicit-anyis relaxed there) - do not reach for it in source to make a test pass.- Keep other Oxc rules satisfied in tests too (block statements, no floating promises -
awaitorvoid). Filenames stay kebab-case.
Discipline
- Never weaken source to make a test pass and never silence a failing test (no blanket skips, no loosened types). Fix the cause, or stop and report the exact command and output. See guardrails.mdc.
- When you change a wire shape or constrained value set, update the tests that assert it in the same change.
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 · 21 lines · 390 tokens per session scan A 614334b61c92
testing is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 390 tokens. 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
testing
Always use vitest for testing. Use describe/it blocks.
android_unit_testing_bdd
Unit testing best practices with BDD style.
testing-pyramid-agent
Provides guidance on testing pyramid principles and how to analyze test distribution. Use this rule when discussing test distribution, test strategy, or when analyzing test coverage across unit, integration, and E2E tests.
vue-test-utils-auto
@vue/test-utils Standards for Vue 3 components and Vitest.
react-component-hook-testing-auto
Enforces best practices for unit testing React components and custom hooks using React Testing Library and Vitest.
vitest-best-practices-auto
Enforces best practices for Vitest unit tests.