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 skills add curiositech/some_claude_skills --skill form-validation-architectgit clone --depth 1 https://github.com/curiositech/some_claude_skillsWrote 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/skills/curiositech/some_claude_skills/form-validation-architect)<a href="https://agentmods.dev/skills/curiositech/some_claude_skills/form-validation-architect"><img src="https://agentmods.dev/badge/skills/curiositech/some_claude_skills/form-validation-architect/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/skills/curiositech/some_claude_skills/form-validation-architect"><img src="https://agentmods.dev/badge/skills/curiositech/some_claude_skills/form-validation-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.03820 |
| Opus 5 | $0.00046 | $0.01910 |
| Sonnet 5 | $0.00018 | $0.00764 |
| Haiku 4.5 | $0.00009 | $0.00382 |
Grade A, and why
form-validation-architect 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 6d 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 — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form Validation Architect
Expert in building production-grade form systems with client-side validation, type safety, and excellent UX.
When to Use
✅ Use for:
- Complex forms with multiple fields and validation rules
- Multi-step wizards with progress tracking
- Dynamic field arrays (add/remove items)
- Form state persistence across sessions
- Async validation (check username availability, validate address)
- Dependent fields (enable B when A is checked)
- File uploads with progress and validation
- Autosave and optimistic updates
❌ NOT for:
- Simple contact forms (HTML + basic JS is fine)
- Backend-only validation (use Joi, Yup on server)
- Non-React frameworks (use Formik alternatives)
- Read-only displays (no form needed)
Quick Decision Tree
Does your form:
├── Have >5 fields? → Use react-hook-form
├── Need type safety? → Add Zod schemas
├── Have dynamic fields? → Use field arrays
├── Span multiple steps? → Use wizard pattern
├── Need async validation? → Use resolver + async rules
└── Just email/message? → Use native HTML validation
Technology Selection (2024+)
React Hook Form (Recommended)
Why RHF over Formik:
- Performance: Uncontrolled inputs → fewer re-renders
- Bundle size: 8KB vs 30KB (Formik)
- DevEx: Better TypeScript support
- Adoption: 40k+ stars, industry standard 2023+
Timeline:
- 2015-2019: Formik dominated
- 2019: React Hook Form released
- 2022+: RHF became standard
- 2024: Formik in maintenance mode
Zod for Schema Validation
Why Zod over Yup:
- TypeScript-first: Infer types from schemas
- Composability: Better schema reuse
- Error messages: More customizable
- Modern: Active development, latest features
Timeline:
- 2017-2020: Yup standard
- 2020: Zod released
- 2023+: Zod preferred for new projects
Common Anti-Patterns
Anti-Pattern 1: Controlled Inputs Everywhere
Novice thinking: "All form inputs should be controlled with useState"
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .claude-plugin/plugin.json 465 B
- assets/form-templates/LoginForm.tsx 3.9 KB
- assets/form-templates/MultiStepWizard.tsx 9.7 KB
- assets/form-templates/RegistrationForm.tsx 5.9 KB
- references/accessibility.md 10 KB
- references/file-upload.md 14 KB
- references/zod-patterns.md 8.9 KB
- scripts/generate_form.ts 4.7 KB runs code
- scripts/validate_schemas.ts 6.8 KB runs code
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.
- 6d ago First seen · 587 lines · 91 tokens per session scan A 6a810a8e5bab
form-validation-architect is a skill published in the GitHub repository curiositech/some_claude_skills (218 stars, last pushed 4d ago), licensed MIT. It adds 91 tokens to every session and 3,820 once invoked, about $0.0005 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 skills, from other repositories
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
dashboard-widgets
Author a dashboard widget — a small React component backed by named LangWatchQL queries — from a plain question. Discovers the analytics schema, writes the queries, writes the widget file, saves it, then proves it renders. Use when asked to build, prototype, or iterate on a custom chart widget, or to add a widget…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…