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/front-reactgit 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/front-react)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/front-react"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/front-react.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.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
front-react 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
Front-app Vitest
General: vitest.mdc. Discipline: testing.mdc. DOM/RTL harness depth: skill front-vitest. Never use the Workers pool on front-*.
Repo invariants
- Config:
defineNodeConfig+resolvePackageRoot(import.meta.dirname)forroot/test.dirfrom@repo/vitest-config(Node). NevercloudflareTest. - Prefer Node unit tests for
services/,utils/,*-query-options: isolatedQueryClientwithretry: falseandgcTime: Infinity; exercise sharedqueryOptionsviafetchQuery/ensureQueryData. Do not reusesrc/config/query-client.tsacross tests withoutclear. - Never hand-edit
src/routeTree.gen.ts- regenerate with approutes:generate/routes:check. - Imports from
vitestonly; in-app paths via#/*. Typecheck viatests/tsconfig.json(in packagecheck-types). - Agents:
pnpm turbo run test --filter=front-app(non-watch). - DOM harness installed: happy-dom +
@testing-library/react/jest-dom/user-event(catalog deps). Config-wide environment staysnode; a DOM suite opts in per file with// @vitest-environment happy-domon line 1.vitest.setup.tssets the React 19 act flag for every suite, and imports the jest-dom matchers plusafterEach(cleanup)only when a DOM environment is present (globals are off, so RTL auto-cleanup never registers) - a Node suite must not pay the ~600ms harness import..tsxtest files are matched. Canonical example:tests/components/ui/button.test.tsx. Depth: skillfront-vitest. - happy-dom is the deliberate default (speed on constrained hardware). If a suite hits a happy-dom spec gap, switch that one file to
@vitest-environment jsdomafter adding the dep - do not change the config-wide environment.
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 · 20 lines · 0 tokens per session scan A bbc6b1a89d49
front-react 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 512 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
react-component-hook-testing-auto
Enforces best practices for unit testing React components and custom hooks using React Testing Library and Vitest.
testing-react
Testing React components — React Testing Library, hooks, context, async, accessibility. Extends core/rules/testing.mdc with React-specific patterns.
testing
Always use vitest for testing. Use describe/it blocks.
android_unit_testing_bdd
Unit testing best practices with BDD style.
cursorrules
Use functional components in React. Prefer Tailwind CSS classes.
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.