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/obviousworks/vibe-coding-ai-rules/101-react-patternsgit clone --depth 1 https://github.com/obviousworks/vibe-coding-ai-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.00000 | $0.00229 |
| Opus 5 | $0.00000 | $0.00114 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
101-react-patterns 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 2d 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 Patterns
Component Structure
- Functional components only (no class components)
- Server Components by default; Client Components ('use client') only when needed
- Extract business logic into custom hooks or service layer
- Max 200 lines per component file
State Management
- Local state: useState/useReducer
- Server state: React Query / SWR
- Global state: Zustand (or specified alternative)
- URL state: nuqs or searchParams
Performance
- Use React.memo() only with measured performance issues
- Implement proper key props for lists
- Lazy load heavy components with React.lazy() + Suspense
- Use optimistic updates for better UX
Error Handling
- Implement Error Boundaries for fault isolation
- Use proper loading/error/empty states for async data
- Never swallow errors silently
Accessibility
- All interactive elements need keyboard support
- Use semantic HTML elements
- Include proper ARIA labels where needed
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.
- 2d ago First seen · 36 lines · 0 tokens per session scan A b6637fc16406
101-react-patterns is a cursor rule published in the GitHub repository obviousworks/vibe-coding-ai-rules (88 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 229 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
tools
(none|read|write|network|exec) and risk (low|medium|high|critical). These drive the permission classifier — be honest.
ios-app-store-validator
App Store validation for iOS projects.
task_structure_example.mouse
TaskID: MOUSE#TASK0001 # Example. MUST be unique & sequential. Title: "Example Task: Process User Survey Data and Generate Insights Report" Description: | This task involves processing raw user survey data, performing analysis, and generating a comprehensive insights report.
Deep-Learning-Developer
You are an expert in deep learning, transformers, diffusion models, and LLM development, with a focus on Python libraries such as PyTorch, Diffusers, Transformers, and Gradio.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.