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/goranerhartic/cursor-development-rules/formsgit clone --depth 1 https://github.com/GoranErhartic/cursor-development-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/goranerhartic/cursor-development-rules/forms)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/forms"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/forms.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.00013 | $0.00696 |
| Opus 5 | $0.00006 | $0.00348 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
forms 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form Patterns
Setup (React Hook Form + Zod)
useForm<T>({ resolver: zodResolver(schema), defaultValues })— inferTwithz.infer<typeof schema>- Inline errors:
formState.errors.field?.message; setaria-invalid={!!errors.field}on input - Disable submit:
disabled={isSubmitting}ordisabled={!isDirty || isSubmitting}
// Skeletal: RHF + Zod
const schema = z.object({ email: z.string().email(), password: z.string().min(8) });
type FormData = z.infer<typeof schema>;
const { register, handleSubmit, formState: { errors, isSubmitting } } = useForm<FormData>({
resolver: zodResolver(schema),
defaultValues: { email: '', password: '' },
});
// onSubmit: async (data) => { await api.submit(data); }
// JSX: <form onSubmit={handleSubmit(onSubmit)}> ... <input {...register('email')} aria-invalid={!!errors.email} /> ...
Key Hooks
- useFieldArray: Dynamic lists —
name: 'contacts',append,remove; registercontacts.${index}.field - useFormContext: Nested forms / shared context — wrap with
FormProvider, consume withuseFormContext - useWatch: Subscribe to specific fields for conditional UI or side effects
- setValue / reset: Programmatic values (e.g. after load); reset after successful submit — prefer
reset()in effect or after mutate, not inside onSubmit
Conventions
- Zod schema at boundary; type from
z.infer; show field errors inline; disable submit during submit; server errors viasetError('root.serverError', { message })or per-fieldsetError(field, { message }) - Multi-step: one form per step or single form with
useFormContext; persist state as needed
Controlled vs Uncontrolled
- Prefer React Hook Form (uncontrolled by default) for most forms
- Controlled:
value+onChangewhen you need full control (e.g. custom components) - Do not mix controlled and uncontrolled for the same field
API Integration
- On mutation error: map API validation errors to fields with
setError(field, { message }); usesetError('root', { message })for generic errors - Use
useMutation(TanStack Query) withmutateAsyncin onSubmit; handle loading viaisSubmittingor mutation state
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.
- yesterday First seen · 57 lines · 13 tokens per session scan A 7515057bd426
forms is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 696 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
mobx
Definitive guidelines for structuring MobX applications with React, focusing on predictable state management, optimal rendering, and modern best practices.
new-component
Workflow for creating new React components.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.