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/jalcantarab/v0-vibecodex/react-componentsgit clone --depth 1 https://github.com/jalcantarab/v0-vibecodexWrote 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/jalcantarab/v0-vibecodex/react-components)<a href="https://agentmods.dev/rules/jalcantarab/v0-vibecodex/react-components"><img src="https://agentmods.dev/badge/rules/jalcantarab/v0-vibecodex/react-components.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.00723 | $0.00723 |
| Opus 5 | $0.00362 | $0.00362 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
react-components 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Component Development Guidelines
Component Structure
Always use functional components with hooks. Follow this structure:
import { ComponentProps } from 'react'
import { cn } from '@/lib/utils'
interface ComponentNameProps extends ComponentProps<'div'> {
// Add specific props here
}
export function ComponentName({ className, ...props }: ComponentNameProps) {
return (
<div className={cn("base-classes", className)} {...props}>
{/* Component content */}
</div>
)
}
Key Patterns
1. Component Naming
- Use PascalCase for component names
- Use descriptive, semantic names
- Export as named exports, not default exports
2. Props Handling
- Extend HTML element props when appropriate
- Use
cn()utility for className merging - Destructure props with rest operator for HTML attributes
3. Styling Approach
- Use Tailwind CSS classes
- Leverage shadcn/ui components as base
- Use CSS variables for theming
- Maintain consistent spacing with
space-y-6,gap-6
4. Layout Patterns
// Standard page layout
<div className="flex flex-col min-h-screen">
<div className="container py-10 max-w-6xl mx-auto px-4 sm:px-6 lg:px-8">
{/* Page content */}
</div>
</div>
// Two-column layout
<div className="grid gap-6 md:grid-cols-[2fr_1fr]">
<div className="space-y-6">
{/* Main content */}
</div>
<div className="space-y-6">
{/* Sidebar */}
</div>
</div>
5. Card Components
import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card'
<Card className="hover:bg-muted/50 transition-colors">
<CardHeader>
<CardTitle>Title</CardTitle>
</CardHeader>
<CardContent>
{/* Content */}
</CardContent>
</Card>
6. Badge Usage
// Open source indicator
<Badge variant="outline" className="px-3 py-1 border-violet-200 bg-violet-100/50 text-violet-800">
Open Source
</Badge>
// Difficulty level
<Badge className="bg-cyan-600">Beginner</Badge>
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 · 120 lines · 723 tokens per session scan A c063615a90e0
react-components is a cursor rule published in the GitHub repository jalcantarab/v0-vibecodex (8 stars, last pushed 1y ago), licensed MIT. It adds 723 tokens to every session, about $0.0036 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
nextjs
Next.js with TypeScript and Tailwind UI best practices.
react
React best practices and patterns for modern web applications.
tailwindcss
Tailwind CSS and UI component best practices for modern web applications.
5-frontend-styling
This document outlines conventions for building the user interface with React and styling it with Tailwind CSS.
general
Wonder Blocks design system conventions, component patterns, and coding standards.
frontend-best-practices
Standards for modern Frontend development using Next.js 16 (App Router), React 19, Tailwind CSS v4, and Shadcn/UI. Apply when working on apps/web or packages/ui.