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/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/react)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/react"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/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.00448 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
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 3d 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
React (19) Component & Hook Rules
These apps are client-only Vite SPAs - no SSR, no React Server Components, no "use server". Ignore general React guidance framed around those. For a targeted performance audit load vercel-react-best-practices (browser/client guidance only).
Split of concerns
- Server/async state → tanstack-query.mdc. Never fetch in
useEffect. - Routing / URL state → tanstack-router.mdc.
- Vite, providers, env, splitting → frontend-architecture.mdc.
- Naming → naming.mdc; lint → code-style.mdc.
Repo invariants
- Never define a component (or
memo/lazywrapper) inside another component's body - hoist to module scope. - Prefer deriving during render over syncing props/state in
useEffect. Effects only for external sync; clean up on unmount. - React Compiler on (see frontend-architecture): do not default to
useMemo/useCallback/memo. Escape hatch only when needed. - Prefer
useTransition/startTransition/useDeferredValuefor non-urgent or expensive UI work. - List keys: stable identity (
item.id), not index when order can change. - React 19:
refis a normal prop (no newforwardRef).use()only with a stable cached promise under<Suspense>- neveruse(fetch(...))created during render. - Error boundaries at tree/lazy route edges; route errors via router's
errorComponent. a11y partly linted (jsx-a11yonapps/front-*/src/**).
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.
- 3d ago First seen · 27 lines · 0 tokens per session scan A 0c7f4b916787
react is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 448 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-08-30.
Other cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
testing
Always use vitest for testing. Use describe/it blocks.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.
swift-observable
Migration guide for updating SwiftUI apps from ObservableObject to the @Observable macro.
update-docs
You will generate LLM-optimized documentation with concrete file references and flexible formatting.