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/jimmypocock/cursor-rules/reactgit clone --depth 1 https://github.com/jimmypocock/cursor-rulesWhat 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.00003 | $0.00923 |
| Opus 5 | $0.00002 | $0.00462 |
| Sonnet 5 | $0.00001 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00092 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description: React Development Standards Globs: **/.tsx, **/.jsx, */.ts, **/.js, /components//, /hooks//, /context//
React Development Standards
@base.mdc @typescript.mdc
Component Architecture
- Use functional components with hooks instead of class components
- Keep components focused on a single responsibility
- Create small, reusable UI components
- Implement proper component composition
- Separate UI components from container components
- Use proper prop types with TypeScript
- Structure components with a logical folder organization
- Create presentational/UI components separate from data containers
Hooks Usage
- Follow the Rules of Hooks consistently
- Use useState for component state management
- Implement useEffect with proper dependencies
- Create custom hooks for reusable logic
- Use useCallback for memoized callbacks
- Implement useMemo for expensive calculations
- Apply useRef for persisted mutable values
- Use context hooks for global state access
State Management
- Use local state for component-specific state
- Implement React Context for shared state
- Use proper state management libraries for complex state
- Keep state normalized and minimal
- Implement proper state initialization
- Use state update functions instead of direct assignment
- Create proper state update patterns
- Implement state persistence when needed
Performance Optimization
- Use React.memo for pure components
- Implement proper key usage in lists
- Use windowing for long lists (react-window/react-virtualized)
- Implement proper loading and lazy states
- Apply code splitting with React.lazy
- Use Suspense for async operations
- Implement proper bundle optimization
- Avoid unnecessary renders with proper dependencies
Event Handling
- Use proper event handler naming (handleEventName)
- Implement event handler functions efficiently
- Use synthetic events properly
- Apply proper event propagation control
- Use debouncing/throttling for frequent events
- Implement proper form submission handling
- Create controlled components for form elements
- Apply proper validation for user inputs
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 · 143 lines · 3 tokens per session scan A 08e36b52f623
react is a cursor rule published in the GitHub repository jimmypocock/cursor-rules (8 stars, last pushed 1y ago), licensed MIT. It adds 3 tokens to every session and 923 once invoked, about $0.0000 per session on Opus 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-08-31.
Other cursor rules, from other repositories
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
mobile
Rules for mobile development (Swift/iOS, Kotlin Android, React Native, Flutter).
java-kotlin
Rules applied when working in Java or Kotlin files (incl. Android).
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
00-global-architect
Global default behavior for the entire repository.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.