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/oakensoul/nextjs-cursor-prompts/component-create-formgit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/component-create-form)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-create-form"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-create-form.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.00000 | $0.02718 |
| Opus 5 | $0.00000 | $0.01359 |
| Sonnet 5 | $0.00000 | $0.00544 |
| Haiku 4.5 | $0.00000 | $0.00272 |
Grade A, and why
component-create-form 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 4d 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form Component Creation Request
Please create a new form component following our specialized form patterns and validation standards:
🎯 FORM CREATION OBJECTIVES:
- IMPLEMENT comprehensive validation using Zod schemas with real-time feedback
- ENSURE accessibility compliance with proper ARIA attributes and form semantics
- INTEGRATE with NextJS patterns including server actions and form submission flows
- PROVIDE excellent UX with loading states, error handling, and success feedback
- FOLLOW project standards for TypeScript, testing, and component architecture
📋 FORM DEVELOPMENT METHODOLOGY:
STEP 1: Form Planning and Architecture
Determine Form Type and Location:
- Client Component:
src/components/client/forms/- Forms with real-time validation, dynamic inputs - Server Component Integration: Use with server actions for form submission
- Form Categories:
- Authentication Forms: Login, register, password reset (
auth/) - User Input Forms: Profile updates, settings, preferences (
user/) - Content Forms: Contact, feedback, support requests (
content/) - Data Entry Forms: Complex multi-step forms (
data/)
- Authentication Forms: Login, register, password reset (
Form Complexity Assessment:
- Simple Forms: Single-step, basic validation (contact forms, login)
- Complex Forms: Multi-step, conditional fields, file uploads
- Dynamic Forms: Fields that change based on user input
- Validation Requirements: Real-time, server-side, custom validation rules
STEP 2: Schema and Validation Design
Zod Schema Definition:
// Define comprehensive validation schema
const FormSchema = z.object({
email: z.string()
.email('Please enter a valid email address')
.min(1, 'Email is required'),
password: z.string()
.min(8, 'Password must be at least 8 characters')
.regex(/^(?=.*[a-z])(?=.*[A-Z])(?=.*\d)/, 'Password must contain uppercase, lowercase, and number'),
confirmPassword: z.string()
}).refine((data) => data.password === data.confirmPassword, {
message: "Passwords don't match",
path: ["confirmPassword"],
});
type FormData = z.infer<typeof FormSchema>;
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.
- 4d ago First seen · 341 lines · 0 tokens per session scan A 6e637f4f03d4
component-create-form is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,718 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.