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.
git clone --depth 1 https://github.com/obviousworks/vibe-coding-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/obviousworks/vibe-coding-ai-rules/101-react-patterns)<a href="https://agentmods.dev/rules/obviousworks/vibe-coding-ai-rules/101-react-patterns"><img src="https://agentmods.dev/badge/rules/obviousworks/vibe-coding-ai-rules/101-react-patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/obviousworks/vibe-coding-ai-rules/101-react-patterns"><img src="https://agentmods.dev/badge/rules/obviousworks/vibe-coding-ai-rules/101-react-patterns.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00229 |
| Opus 5.5 | $0.00000 | $0.00092 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (93 stars, last pushed 4mo 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
nextjs
Rules for Next.js projects (App Router and Pages Router).
react
Rules for React component files (any framework).
react
React best practices and patterns for modern web applications.
nextjs
Next.js with TypeScript and Tailwind UI best practices.
sample_cursor_rule
React component best practices.
react-components
Always use functional components with hooks. Follow this structure.