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-layoutgit 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-layout)<a href="https://agentmods.dev/skills/aziontech/webkit/webkit-layout"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-layout/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-layout"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-layout.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.00210 | $0.04642 |
| Opus 5.5 | $0.00084 | $0.01857 |
| Sonnet 5.5 | $0.00042 | $0.00928 |
| Haiku 4.5 | $0.00021 | $0.00464 |
Grade A, and why
webkit-layout 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 23d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-layout
Purpose
A page makes exactly three layout decisions: how far its content sits from the app chrome
(boundary), how wide the content column may get (measure), and how far things sit from each
other (rhythm). @aziontech/theme ships all three as layout-* utilities and tokens, so a page
names its decisions instead of re-deriving them.
This matters more than it sounds. A hand-rolled mx-auto max-w-(--container-7xl) is correct on the
page you write it on and wrong on the next one, because nothing ties the two together: one page caps
at 7xl, the sibling tab caps at 6xl, the sticky footer under them caps at neither, and the
buttons drift right of the form they submit. Naming the decision makes alignment structural — the
scrolling body and its action bar align because they carry the same class, not because two numbers
happened to match.
How to use
/webkit-layout— shape any page in this conversation with the system below./webkit-layout <file>— review that page: per gap report the quoted line, the rule it breaks in one sentence, and the concrete fix.
Related: /webkit-lists (the index page this shape carries) · /webkit-create-surface (page vs
drawer, and the commit bar that must align with its form) · /webkit-navigation (the shell that owns
the boundary on a padded page) · /webkit-baseline-ui (tokens, typography, spacing scale).
When to invoke
- Starting any new page, or asking how wide it should be.
- Adding a sticky action bar, tab bar, or footer under a scrolling body.
- Reviewing a page whose content drifts to the left edge on a wide screen, whose bar misaligns with the body above it, or whose sections breathe unevenly.
- You are about to write
mx-auto,max-w-,w-full, or a page-levelp-(--spacing-*). - The page changes width between two states (empty vs populated) or between two sibling tabs.
1. Three levels, and no fourth
Every page is the same three nested decisions. Each level owns exactly one, and no level restates another's.
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.
- 23d ago First seen · 351 lines · 210 tokens per session scan A eecea2fe3ca2
webkit-layout is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 210 tokens to every session and 4,642 once invoked, about $0.0008 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-23.
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.