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-update-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-update-form)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-form"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-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.1 | $0.00000 | $0.04223 |
| Opus 5 | $0.00000 | $0.02112 |
| Sonnet 5 | $0.00000 | $0.00845 |
| Haiku 4.5 | $0.00000 | $0.00422 |
Grade A, and why
component-update-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 5d 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 — 625 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form Component Update Request
Please update and enhance an existing form component following our improvement patterns and enhancement standards:
🎯 FORM UPDATE OBJECTIVES:
- ENHANCE validation systems with improved rules, real-time feedback, and error handling
- IMPROVE accessibility with better ARIA attributes, keyboard navigation, and screen reader support
- OPTIMIZE user experience with loading states, success feedback, and form flow improvements
- UPGRADE technical implementation with better TypeScript, performance optimizations, and modern patterns
- MAINTAIN backward compatibility while implementing meaningful improvements
📋 FORM UPDATE METHODOLOGY:
STEP 1: Current Form Assessment
Analyze Existing Implementation:
- Current validation approach: Review existing Zod schemas and validation logic
- Accessibility audit: Test current ARIA attributes and keyboard navigation
- User experience gaps: Identify missing loading states, error handling, success feedback
- Performance issues: Review re-render patterns and optimization opportunities
- TypeScript completeness: Check interface coverage and type safety
Identify Enhancement Opportunities:
// Assessment checklist for form improvements
interface FormAudit {
validation: {
realTimeValidation: boolean;
serverValidation: boolean;
customRules: boolean;
errorRecovery: boolean;
};
accessibility: {
properLabels: boolean;
ariaDescriptions: boolean;
keyboardNavigation: boolean;
screenReaderSupport: boolean;
};
userExperience: {
loadingStates: boolean;
successFeedback: boolean;
progressIndicators: boolean;
autoSave: boolean;
};
performance: {
optimizedRendering: boolean;
efficientValidation: boolean;
memoryManagement: boolean;
};
}
STEP 2: Validation Enhancement Patterns
Advanced Validation Improvements:
// Enhanced validation with contextual feedback
const enhancedFormSchema = z.object({
email: z.string()
.min(1, 'Email is required')
.email('Please enter a valid email address')
.refine(async (email) => {
// Server-side validation for uniqueness
const exists = await checkEmailExists(email);
return !exists;
}, 'This email is already registered'),
password: z.string()
.min(8, 'Password must be at least 8 characters')
.regex(/^(?=.*[a-z])/, 'Must contain at least one lowercase letter')
.regex(/^(?=.*[A-Z])/, 'Must contain at least one uppercase letter')
.regex(/^(?=.*\d)/, 'Must contain at least one number')
.regex(/^(?=.*[@$!%*?&])/, 'Must contain at least one special character'),
confirmPassword: z.string()
}).refine((data) => data.password === data.confirmPassword, {
message: "Passwords don't match",
path: ["confirmPassword"],
});
// Real-time validation with debouncing
const useEnhancedValidation = (schema: ZodSchema) => {
const [errors, setErrors] = useState<Record<string, string>>({});
const [isValidating, setIsValidating] = useState<Record<string, boolean>>({});
const validateField = useCallback(
debounce(async (fieldName: string, value: any) => {
setIsValidating(prev => ({ ...prev, [fieldName]: true }));
try {
await schema.shape[fieldName].parseAsync(value);
setErrors(prev => ({ ...prev, [fieldName]: '' }));
} catch (error) {
if (error instanceof ZodError) {
setErrors(prev => ({
...prev,
[fieldName]: error.errors[0]?.message || 'Invalid value'
}));
}
} finally {
setIsValidating(prev => ({ ...prev, [fieldName]: false }));
}
}, 300),
[schema]
);
return { errors, isValidating, validateField };
};
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.
- 5d ago First seen · 625 lines · 0 tokens per session scan A fc4407c3a051
component-update-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 4,223 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.