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/Farzannajipour/cursor-react-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/farzannajipour/cursor-react-rules/component-patterns)<a href="https://agentmods.dev/rules/farzannajipour/cursor-react-rules/component-patterns"><img src="https://agentmods.dev/badge/rules/farzannajipour/cursor-react-rules/component-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/farzannajipour/cursor-react-rules/component-patterns"><img src="https://agentmods.dev/badge/rules/farzannajipour/cursor-react-rules/component-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.01161 |
| Opus 5.5 | $0.00000 | $0.00464 |
| Sonnet 5.5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
component-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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Creation Patterns
Reusable templates for generating React components following project standards.
Pattern: Basic Component
interface [ComponentName]Props {
children?: React.ReactNode;
className?: string;
}
export function [ComponentName]({ children, className }: [ComponentName]Props) {
return (
<div className={cn('[base-classes]', className)}>
{children}
</div>
);
}
Pattern: Component with Variants (CVA)
import { cva, type VariantProps } from 'class-variance-authority';
import { cn } from '@/lib/utils';
const [componentName]Variants = cva(
'[base-classes]',
{
variants: {
variant: {
primary: '[primary-classes]',
secondary: '[secondary-classes]',
},
size: {
sm: '[sm-classes]',
md: '[md-classes]',
lg: '[lg-classes]',
},
},
defaultVariants: {
variant: 'primary',
size: 'md',
},
}
);
interface [ComponentName]Props
extends React.HTMLAttributes<HTMLDivElement>,
VariantProps<typeof [componentName]Variants> {}
export function [ComponentName]({
className,
variant,
size,
...props
}: [ComponentName]Props) {
return (
<div
className={cn([componentName]Variants({ variant, size }), className)}
{...props}
/>
);
}
Pattern: Form Component with React Hook Form + Zod
import { useForm } from 'react-hook-form';
import { zodResolver } from '@hookform/resolvers/zod';
import { z } from 'zod';
const schema = z.object({
email: z.string().email('Invalid email'),
password: z.string().min(8, 'Min 8 characters'),
});
type FormData = z.infer<typeof schema>;
export function [FormName]({ onSubmit }: { onSubmit: (data: FormData) => Promise<void> }) {
const { register, handleSubmit, formState: { errors, isSubmitting } } = useForm<FormData>({
resolver: zodResolver(schema),
});
return (
<form onSubmit={handleSubmit(onSubmit)} className="space-y-4">
<div>
<label htmlFor="email">Email</label>
<input {...register('email')} id="email" type="email" />
{errors.email && <p className="text-red-600">{errors.email.message}</p>}
</div>
<button type="submit" disabled={isSubmitting}>
{isSubmitting ? 'Submitting...' : 'Submit'}
</button>
</form>
);
}
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 · 199 lines · 0 tokens per session scan A 4577a881f356
component-patterns is a cursor rule published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,161 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
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.