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 andrewsrigom/agent-skills --skill shadcn-forms-and-field-primitivesgit clone --depth 1 https://github.com/andrewsrigom/agent-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/andrewsrigom/agent-skills/shadcn-forms-and-field-primitives)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/shadcn-forms-and-field-primitives"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/shadcn-forms-and-field-primitives/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/andrewsrigom/agent-skills/shadcn-forms-and-field-primitives"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/shadcn-forms-and-field-primitives.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.00060 | $0.00734 |
| Opus 5 | $0.00030 | $0.00367 |
| Sonnet 5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
shadcn-forms-and-field-primitives 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 11d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shadcn Forms And Field Primitives
Use this skill when the task is about form UI structure, not when it is purely about a form-state library in isolation.
Scope
- field primitives and form presentation
- choosing a form-state strategy
- keeping validation and UI responsibilities separate
- integrating shadcn fields with
react-hook-formor another chosen form-state layer - deciding when the problem is really form-state orchestration rather than field presentation
Routing cues
- shadcn forms, field primitives,
react-hook-form,Controller,Field, form layout, input validation presentation, error text, helper text, or deciding how to structure a product form -> use this skill - if the task is mainly about complex form-state orchestration, async field reactivity, or large dynamic field arrays, solve that in the chosen form-state layer instead of forcing the visual field layer to own it
Default path
- Pick one form-state strategy per app or feature and stay consistent.
- Use shadcn field primitives for structure, labels, descriptions, and errors.
- Keep validation logic in the schema or form-state layer, not buried inside visual components.
- Keep submission side effects at the mutation or action boundary, not inside field wrappers.
- Keep the field layer focused on structure and presentation when the problem becomes mostly about form-state orchestration.
When to deviate
- Use
react-hook-formwhen the app already standardizes on it and the flow is straightforward. - Use a richer form-state layer only when the app actually needs stronger reactive state, richer async handling, or large dynamic form behavior.
- Build field-specific wrappers only when the same structure and validation presentation repeat across the product.
Guardrails
- one form-state strategy per surface is better than mixing libraries casually
- field components should present state, not own business logic
- server validation still matters even when client validation is rich
- form wrappers should reduce duplication, not obscure the underlying state model
What ships with it
1 file 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.
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.
- 11d ago First seen · 72 lines · 60 tokens per session scan A 2921dae2a9c1
shadcn-forms-and-field-primitives is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 734 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…