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 aziontech/webkit --skill webkit-formgit clone --depth 1 https://github.com/aziontech/webkitWrote 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/aziontech/webkit/webkit-form)<a href="https://agentmods.dev/skills/aziontech/webkit/webkit-form"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-form/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/aziontech/webkit/webkit-form"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-form.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.00172 | $0.12953 |
| Opus 5.5 | $0.00069 | $0.05181 |
| Sonnet 5.5 | $0.00034 | $0.02591 |
| Haiku 4.5 | $0.00017 | $0.01295 |
Grade A, and why
webkit-form 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.
How it starts
The opening of the file, as written. The whole thing — 1,014 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-form
Purpose
Forms are where a product is most keyboard- and screen-reader-tested and most often fails: a label
that is really a placeholder, a select whose <label for> points at nothing, a validation error shown
only in colour, a field that never says it was required. This skill fixes the accessibility of a form
built on @aziontech/webkit so it is operable by keyboard, understandable by a screen reader, and
recoverable when it rejects input. It is the a11y companion to /webkit-ux-heuristics
(which establishes the states) and /webkit-ui-states (which locks the scope and
toasts request errors) — this skill owns layout, labels, grouping, validation semantics, and submit.
There are two ways to lay out a form, and both are first-class:
- Approach A — Cards + ItemGroups. Sections are a flush
CardBoxwrapping anItem.List; every field is oneItemrow (name/guidance on the left, control on the right). This is the default for grouped, settings-style, or list-like forms — an account settings page, a resource's config or create page, a create drawer. - Approach B — Fields separated. Standalone
field-*triads stacked in a column. This is for short, focused, single-purpose forms — a sign-in flow, a rename or delete-confirmation dialog, a short create drawer, a single step in a wizard.
Pick one per form; don't mix row-fields and stacked-fields in the same section.
How to use
/webkit-formApply the layout + patterns below to any form you build in this conversation./webkit-form <file>Review the file's form against the patterns and output, per gap:- the exact line / element (quoted),
- which pattern it breaks (1 short sentence),
- the concrete fix, naming the webkit component to use.
When to invoke
- Building or reviewing any create/edit page, settings panel, drawer form, or multi-field form.
- The user asks "is this form accessible", "wire up the labels", "the screen reader skips this", "where do errors go", "which layout for this form".
- After
/webkit-ux-heuristicsestablishes the states and before/webkit-ui-stateslocks the async submit.
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 · 1,014 lines · 172 tokens per session scan A 861cd0ffaf9c
webkit-form is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 172 tokens to every session and 12,953 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
design-doctrine
The house rules for ANY design or UI work - the verification protocol (run the gate, never claim a number), the absolute no-emoji rule, token by intent, one shared theme, the eight states, one thing leads, and output completeness. Load this FIRST whenever building, reviewing, or theming a screen, component, or token…
image-to-code
Turn a reference image, screenshot, or mockup into token-driven, accessible code — infer the design system from the reference (palette, type scale, spacing, radius, layout archetype), map it to the 3-tier tokens, rebuild it, then verify with the kit's gates. Use when the user provides a design/screenshot and wants…
ui-components
UI component library patterns for shadcn/ui and Radix Primitives. Use when building accessible component libraries, customizing shadcn components, using Radix unstyled primitives, or creating design system foundations.
better-design
Build, improve, and review production interfaces with the Better Design MCP. Use for frontend design, UI, UX, interactions, flows, forms, navigation, components, styling, design systems, accessibility, responsive layouts, motion, React Native, Expo, Shopify, Three.js, and product video work, especially when creating…
monochrome
Build accessible UI with monochrome, the framework-agnostic UI library for agents. Use whenever a project depends on monochrome or has ids starting with mct:, mcc:, or mcr:, and whenever you write or fix an accordion, collapsible, dialog or modal, dropdown or context menu, menubar, popover, tabs, or tooltip in HTML…
design
Design workflow that creates design systems, DESIGN.md, and design tokens with anti-pattern enforcement and accessibility checks.