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 skills/sukirman1901/frontend-expert/forms-validationnpx skills add sukirman1901/frontend-expert --skill forms-validationgit clone --depth 1 https://github.com/sukirman1901/frontend-expertWrote 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/sukirman1901/frontend-expert/forms-validation)<a href="https://agentmods.dev/skills/sukirman1901/frontend-expert/forms-validation"><img src="https://agentmods.dev/badge/skills/sukirman1901/frontend-expert/forms-validation.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.00047 | $0.00620 |
| Opus 5 | $0.00023 | $0.00310 |
| Sonnet 5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
forms-validation 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forms & Validation
Overview
Forms must be keyboard-accessible, show clear errors, and never lose user input on soft failures.
When to use
- Any form, wizard, filter bar with submit
- Auth, settings, checkout, create/edit dialogs
When to skip
- Read-only detail with no inputs
- Pure button that is not a form submit
MUST (ship)
| Rule | Detail |
|---|---|
| Labels | Every control has a visible label or aria-label; htmlFor/id associated |
| Errors | Text + association (aria-describedby / equivalent) — not border-only |
| Submit | Pending/disabled while in flight; values kept on 4xx/5xx |
| Focus | On submit failure, move focus to first invalid field |
| Mobile | Primary submit width: 100% below 768; inputs font-size ≥ 16px |
| No Lorem | Real hint/error copy |
| Selects | Product filters / status pickers: prefer custom select (see ui-components) — not bare native OS chrome |
Workflow
- Labels — visible label (or
aria-label); associate withhtmlFor/id - Validation — prefer inline field errors after submit or on blur; don’t block typing with aggressive live errors
- Submit — disable or show pending on the primary button; keep values on error
- Errors — field-level + optional form-level summary with links to fields
- Progressive disclosure — hide advanced fields until needed
- Mobile — full-width primary submit; adequate tap targets (
responsive-ui) - Async submit — pair with
data-fetchingfor retry/toast; never wipe the form on soft fail
Agent boundaries
- May decide: validation timing (submit vs blur), wizard step count, inline vs summary errors
- Must not: invent purple/error hex off-token; skip labels for “clean UI”; use
alert()for validation
Checklist
- Labels + focus order correct
- Error text linked to fields (
aria-describedby/ equivalent) - Pending + error + success submit states
- First invalid field focused after failed submit
- No Lorem placeholder as the only copy
- Full-width primary + ≥16px inputs at 320px
- Works at 320px width (no horizontal overflow)
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 · 65 lines · 47 tokens per session scan A d5c8f7b4a3c0
forms-validation is a skill published in the GitHub repository sukirman1901/frontend-expert (10 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 620 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…