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-baseline-uigit 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-baseline-ui)<a href="https://agentmods.dev/skills/aziontech/webkit/webkit-baseline-ui"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-baseline-ui/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-baseline-ui"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-baseline-ui.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.00055 | $0.03042 |
| Opus 5.5 | $0.00022 | $0.01217 |
| Sonnet 5.5 | $0.00011 | $0.00608 |
| Haiku 4.5 | $0.00006 | $0.00304 |
Grade A, and why
webkit-baseline-ui 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 24d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-baseline-ui
Purpose
Remove AI-generated UI slop from product code built on @aziontech/webkit. This is the opinionated
baseline: real components, real tokens, real typography hierarchy, real spacing rhythm — nothing
hand-rolled, nothing hardcoded.
How to use
/webkit-baseline-uiApply the constraints below to any UI work in this conversation./webkit-baseline-ui <file>Review the file against every constraint and output, per violation:- the exact line / snippet (quoted),
- why it matters (1 short sentence),
- a concrete code-level fix.
When to invoke
- The user asks to "clean up", "deslop", "polish", or "review" a screen / prototype.
- Before shipping any UI composed on top of webkit.
- After scaffolding a screen quickly and wanting a correctness sweep.
Constraints
Components
- MUST compose from
@aziontech/webkitwhenever a primitive exists. To find a component and its flat import path, ask the webkit MCPsuggest_component, or readnode_modules/@aziontech/webkit/catalog.json(imports) — every key is a real subpath (e.g.@aziontech/webkit/button,@aziontech/webkit/input-text,@aziontech/webkit/dialog,@aziontech/webkit/dropdown-menu). - NEVER hand-roll a
<button>, input, modal, tooltip, dropdown, tabs, or divider that webkit ships — this includes a separator. A horizontal/vertical rule is@aziontech/webkit/divider(<Divider />/<Divider orientation="vertical" />), never a hand-rolled<hr>or a<div class="border-t …">/<div class="h-px bg-…">. If you're reaching for a border utility to draw a line between sections, that's the Divider component. (A real, observed failure: a<div>with border classes standing in for the Divider — do not.) - NEVER mix another component library's primitives onto the same surface.
- MUST use
@aziontech/webkit/icon-buttonwith anaria-labelfor icon-only actions. - MUST use
@aziontech/webkit/utils/cn(clsx + tailwind-merge) for any class composition.
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.
- 24d ago Changed · -13 lines ef8f0ceb48a9
- 1mo ago First seen · 209 lines · 55 tokens per session scan A 089d26062f52
webkit-baseline-ui is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 3,042 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-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.