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/form-patterns)<a href="https://agentmods.dev/rules/farzannajipour/cursor-react-rules/form-patterns"><img src="https://agentmods.dev/badge/rules/farzannajipour/cursor-react-rules/form-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/form-patterns"><img src="https://agentmods.dev/badge/rules/farzannajipour/cursor-react-rules/form-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.01336 |
| Opus 5.5 | $0.00000 | $0.00534 |
| Sonnet 5.5 | $0.00000 | $0.00267 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
form-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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form Patterns
React Hook Form + Zod
Basic Form
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 LoginForm() {
const { register, handleSubmit, formState: { errors, isSubmitting } } = useForm<FormData>({
resolver: zodResolver(schema),
});
const onSubmit = async (data: FormData) => {
await login(data);
};
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>
<div>
<label htmlFor="password">Password</label>
<input {...register('password')} id="password" type="password" />
{errors.password && <p className="text-red-600">{errors.password.message}</p>}
</div>
<button type="submit" disabled={isSubmitting}>
{isSubmitting ? 'Logging in...' : 'Log In'}
</button>
</form>
);
}
Multi-Step Form
const [step, setStep] = useState(1);
const schema = z.object({
// Step 1
personal: z.object({
name: z.string().min(1),
email: z.string().email(),
}),
// Step 2
address: z.object({
street: z.string().min(1),
city: z.string().min(1),
}),
});
// Validate current step only
const stepSchemas = {
1: schema.pick({ personal: true }),
2: schema.pick({ address: true }),
};
const nextStep = async () => {
const isValid = await trigger(); // Validate current step
if (isValid) setStep(step + 1);
};
Form with Server Action
'use client';
import { useFormState, useFormStatus } from 'react-dom';
import { createPost } from './actions';
export function PostForm() {
const [state, formAction] = useFormState(createPost, null);
return (
<form action={formAction} className="space-y-4">
<div>
<label htmlFor="title">Title</label>
<input name="title" id="title" required />
{state?.errors?.title && (
<p className="text-red-600">{state.errors.title}</p>
)}
</div>
<SubmitButton />
</form>
);
}
function SubmitButton() {
const { pending } = useFormStatus();
return (
<button type="submit" disabled={pending}>
{pending ? 'Creating...' : 'Create Post'}
</button>
);
}
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 · 233 lines · 0 tokens per session scan A f17ef6feab35
form-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,336 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.