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 zarpay/rails-template --skill hwc-forms-validationgit clone --depth 1 https://github.com/zarpay/rails-templateWrote 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/zarpay/rails-template/hwc-forms-validation)<a href="https://agentmods.dev/skills/zarpay/rails-template/hwc-forms-validation"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/hwc-forms-validation/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/zarpay/rails-template/hwc-forms-validation"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/hwc-forms-validation.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.00119 | $0.00582 |
| Opus 5.5 | $0.00048 | $0.00233 |
| Sonnet 5.5 | $0.00024 | $0.00116 |
| Haiku 4.5 | $0.00012 | $0.00058 |
Grade A, and why
hwc-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 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.
This is a copy
100% identical to hwc-forms-validation — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Forms & Validation
Implement form-centric Hotwire workflows with Turbo Frames and Stimulus.
Core Workflow
- Identify the form flow: create/edit, inline edit, typeahead, modal form, or external controls.
- Wrap the form interaction scope in a Turbo Frame when validation errors must rerender in place.
- Return
422for validation failures and303for successful redirects. - Handle post-submit behavior with
turbo:submit-endonly when Turbo defaults are insufficient. - Preserve user context during rerenders (focus/caret/selection).
Guardrails
- Keep one source of truth for input state; avoid duplicate controls across frame and non-frame DOM.
- Use the HTML
formattribute for controls rendered outside the target<form>hierarchy. - Avoid firing submit logic on every keystroke without debounce/throttle.
- Keep post-submit behavior explicit when form responses update only a frame.
Load References Selectively
Open only the file needed for the current request.
- Inline editing:
references/2024-02-27-turbo-frames-inline-edit.md - Modal validation flows:
references/2024-05-21-turbo-frames-modals-validation.md - Typeahead search:
references/2023-11-07-turbo-frames-typeahead-search.md - Typeahead validation with focus handling:
references/2025-10-20-turbo-frames-typeahead-validation.md - External form controls in frames:
references/2026-02-03-turbo-frames-external-form.md - Stimulus action parameters for forms:
references/2024-01-16-stimulus-action-parameters.md
Use references/INDEX.md for the full catalog.
Escalate to Neighbor Skills
- Navigation/history/cache behavior: use
hwc-navigation-content - WebSocket or Turbo Stream push updates: use
hwc-realtime-streaming - Media upload/playback behavior: use
hwc-media-content - Generic UX polish (spinners/progress/transitions): use
hwc-ux-feedback - General Stimulus API design questions: use
hwc-stimulus-fundamentals
What ships with it
7 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.
- references/2023-11-07-turbo-frames-typeahead-search.md 4.6 KB
- references/2024-01-16-stimulus-action-parameters.md 5.7 KB
- references/2024-02-27-turbo-frames-inline-edit.md 3.4 KB
- references/2024-05-21-turbo-frames-modals-validation.md 5.7 KB
- references/2025-10-20-turbo-frames-typeahead-validation.md 4.9 KB
- references/2026-02-03-turbo-frames-external-form.md 5.0 KB
- references/INDEX.md 1011 B
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.
- 1mo ago First seen · 46 lines · 119 tokens per session scan A c69d47009b2b
hwc-forms-validation is a skill published in the GitHub repository zarpay/rails-template (12 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 582 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to hwc-forms-validation, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…