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/shumatsumonobu/awesome-ai-rules/reactgit clone --depth 1 https://github.com/shumatsumonobu/awesome-ai-rulesWrote 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/shumatsumonobu/awesome-ai-rules/react)<a href="https://agentmods.dev/rules/shumatsumonobu/awesome-ai-rules/react"><img src="https://agentmods.dev/badge/rules/shumatsumonobu/awesome-ai-rules/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.00277 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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 4d 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 Rules (auto-attached to .tsx/.jsx in packages/web/)
These rules ONLY activate when you're editing React files in the web package. The AI won't see them when editing database code, config files, or anything outside packages/web/*.tsx.
This prevents React-specific advice from leaking into non-React code.
Components
- Server Components by default.
"use client"only at the smallest leaf that needs hooks/events/browser APIs. - Define props as
type ButtonProps = { ... }in the same file. - Use
cn()(clsx + tailwind-merge) for conditional Tailwind classes. - Use
forwardReffor components wrapping native elements.
Data Flow
- Fetch data in Server Components with
async/await. - Use Server Actions for mutations.
useActionStatefor form state,useOptimisticfor instant feedback. - Never use
useEffectfor data fetching.
Routing
- Use
loading.tsxfor streaming,error.tsxfor error boundaries with retry. - Use route groups
(groupName)for layout organization. - Route handlers (
app/api/) are for webhooks only.
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.
- 4d ago First seen · 33 lines · 0 tokens per session scan A 1ba2640a7bc6
react is a cursor rule published in the GitHub repository shumatsumonobu/awesome-ai-rules (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 277 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-31.
Other cursor rules, from other repositories
cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup
Cursor rules for Next.js development with Tailwind CSS and SEO optimization.
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.
cursor-ai-react-typescript-shadcn-ui-cursorrules-p
Cursor rules for Cursor AI development with React, TypeScript, and shadcn/ui integration.
cursorrules
Cursor rule "cursorrules" from Lay4U/awesome-ai-rules, covering cursor go rules, ide-first defaults, go code style, error handling and interfaces and api design.
next-type-llm
Cursor rules for Next.js development with Type LLM integration.
nextjs-app-router-cursorrules-prompt-file
Cursor rules for Next.js development with App Router integration.