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/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/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/louisbrulenaudet/monorepo-template/testing"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/testing.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.01330 | $0.01330 |
| Opus 5.5 | $0.00532 | $0.00532 |
| Sonnet 5.5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
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 23d 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Runtime specifics: hono-workers.mdc (Workers pool), front-react.mdc (front-*). Auditing an existing suite: /review tests (human-invoked).
Toolchain
- Tests live in the package's
tests/directory mirroring the source area, as kebab-case*.test.ts(.tsxinfront-*). Import from"vitest"(no globals), neverjest.*; in-app imports use#/*, never an invented@/alias. - Run through turbo:
pnpm turbo run test --filter=<pkg>; one file:pnpm --filter=<pkg> exec vitest run tests/<path>.test.ts. Packagetestscripts arevitest run; agents never leave watch mode or--uirunning. Turbo cachestestwith no outputs: a hit replays the stored log,--forcere-executes. Smoke-running the dev servers: skillrun-app. - Each app owns a
vitest.config.ts/.mtsbuilt from@repo/vitest-config, pinningroot/test.dirwithresolvePackageRoot(import.meta.dirname)(Vitest VS Code explorer). Two runtimes:worker-*/queue-*/webhook-*/mcp-*→@repo/vitest-config/workers;front-*→@repo/vitest-config(Node). Never the Workers pool or a/workersimport onfront-*, never Node pool knobs on Workers, neverisolate: false/--no-isolateon Workers (it shares binding storage). - No root Vitest config with
test.projectsor the deprecated workspace: Turbo owns the graph. Never merge afront-*app's fullvite.configinto its Vitest config. - Leave
reportersunset so agent / GitHub Actions auto-detection picks the reporter; a custom list must still includeagent. - Prefer real pool bindings on Workers. On Node, mock only true I/O, through
vi.fn/vi.stubGlobalor an injected fake - never module mocking (vi.mock& co. are lint errors viavitest/no-restricted-vi-methods). anyis allowed only in test files (typescript/no-explicit-anyis relaxed there), never in source to make a test pass. Every other Oxc rule still applies (block statements, no floating promises -awaitorvoid).- Tests are deterministic and never depend on test order.
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.
- 23d ago Changed · +6 lines · +343 tokens per session c6c2f15d0e9c
- 25d ago Changed · -23 tokens per session 19ce995a21c5
- 27d ago Changed · +26 lines · +620 tokens per session f8d5d5a67b29
- 1mo ago 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 today), licensed Apache-2.0. It adds 1,330 tokens to every session, about $0.0053 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-09-03.
Other cursor rules, from other repositories
rails-cursorrules-prompt-file
Cursor rules for Rails development with basic setup.
android_unit_testing_bdd
Unit testing best practices with BDD style.
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.
architecture
This document outlines the fundamental architectural principles and patterns for the mcp-debug codebase. Adherence to these guidelines is mandatory to maintain a clean, decoupled, and testable system.
testing
USE WHEN: Writing tests with Vitest, Testing Library and MSW.