enhance-web-forms

enhance-web-forms is a skill for Claude Code from kensaurus/cursor-kenji. It costs 59 tokens per session (1,729 once invoked), scanned A, original, MIT.

A workflow for making web forms accessible, validating their data on both the browser and server, and showing clear responses for each submission state.

In plain words
What is it for?
It is for improving signup, contact, checkout, and multi-step forms with labels, validation, error handling, loading states, success feedback, and recovery after failure.
Why use it?
It helps prevent unlabeled fields, confusing errors, silent submissions, and failed requests that leave users unsure what happened.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cursor-kenji plugin — 132 skills, 63 commands, 6 agents, 1 hook, 3 MCP servers shipped together

Good fit It is for improving signup, contact, checkout, and multi-step forms with labels, validation, error handling, loading states, success feedback, and recovery after failure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kensaurus/cursor-kenji/enhance-web-forms
Install

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.

Any agent
npx skills add kensaurus/cursor-kenji --skill enhance-web-forms
Clone the repo
git clone --depth 1 https://github.com/kensaurus/cursor-kenji

Made for: Claude Code.

Or install cursor-kenji, the plugin that ships this one along with the rest of its 132 skills, 63 commands, 6 agents, 1 hook, 3 MCP servers.

Wrote 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.

agentmods badge for enhance-web-forms

README.md
[![agentmods](https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/enhance-web-forms/github.svg)](https://agentmods.dev/skills/kensaurus/cursor-kenji/enhance-web-forms)
Your own site
<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/enhance-web-forms"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/enhance-web-forms/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.

agentmods 80×15 button for enhance-web-forms

Your own site · 80×15
<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/enhance-web-forms"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/enhance-web-forms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,729 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01729
Opus 5.5 $0.00024 $0.00692
Sonnet 5.5 $0.00012 $0.00346
Haiku 4.5 $0.00006 $0.00173

Measured 1mo ago against content hash bfa2b27866b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

enhance-web-forms 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 1mo 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.

skills/enhance-web-forms/SKILL.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

enhance-web-forms — Production-Quality Forms

Degree of freedom: MIXED. Schema and state-machine judgment [HIGH freedom]; a11y probes and playwright walks [LOW freedom — run exactly].

Forms are where users hand you their data and where apps most often feel broken: unlabeled fields, validation that fires on every keystroke, errors screen readers never announce, a submit button that does nothing visible for three seconds, and no recovery when the request fails. This skill fixes all of that on real forms in the repo.

A form is done when it is accessible, validated on both sides, gives feedback for every state, and recovers from failure. Compile-clean is not done.

Before any browser interaction, read protocol-browser-anti-stall and apply it.

How to reason

  1. Inventory — forms, library, schema; bow out if none
  2. Structure — programmatic labels, types, error association
  3. Parity — one schema both sides; blur + submit, not every keystroke
  4. States — submitting / success / error / unsaved; recover on failure

Worked example

Inventory: signup uses raw <form> + inline if (!email); API validates with zod. Structure: htmlFor labels; autocomplete="email"; aria-invalid + summary. Parity: share the zod schema; validate on blur/submit; map "email taken" to the field. States: submit disables + aria-busy; values preserved on 500; dirty-nav warn.

Self-critique before reporting

  • Labeled — placeholder is never the only name
  • Both sides — client and server rules match; error shapes map to fields
  • Walked — empty, invalid, valid, and server-error paths in the browser
  • Right owner — page/flow UX beyond the form → enhance-web-ux; WCAG sweep → audit-accessibility

Phase 0 — Detect the stack and inventory forms [HIGH freedom]

cat package.json | grep -iE "react-hook-form|formik|@tanstack/react-form|final-form|zod|yup|valibot|superstruct"
rg -n "<form|onSubmit|useForm|handleSubmit" -g "*.{tsx,jsx,vue,svelte}" -l

Read the full file on GitHub · 155 lines

Changes

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.

  1. 1mo ago Changed · -3 tokens per session bfa2b27866b3
  2. 1mo ago First seen · 155 lines · 62 tokens per session scan A 7a5bac3c4d57

Subscribe to this mod's changes

enhance-web-forms is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 59 tokens to every session and 1,729 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

ai-evals-builder

Build AI evals using the Husain-Shankar framework (error analysis, open/axial coding, LLM-as-judge). Use when a user needs to create, improve, or debug evals for an AI product — including defining failure modes, building LLM judges, or setting up production monitoring for an LLM application.

luisabwk/kraken · 72 tokens

test-driven-development

Use when implementing any feature, bugfix, or code change - write tests first, watch them fail, then implement.

luisabwk/kraken · 23 tokens

patrol-e2e-testing

Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).

evanca/flutter-ai-rules · 43 tokens

mocktail

Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).

evanca/flutter-ai-rules · 34 tokens

instruction-ablation

Rebuild a minimal instruction set from evidence: confirm a bare baseline, run one real task in-session under guardrails only, log struggles, and add an instruction only after the same failure repeats; retest and keep only if verification improves. Use when the user invokes /instruction-ablation or asks to ablate…

emaraschio/cursor-commands · 78 tokens

component-creation

Step-by-step workflow for creating accessible, tested UI components. Use when the user asks to create a new UI component.

girijashankarj/cursor-handbook · 28 tokens