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-create-surfacegit 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-create-surface)<a href="https://agentmods.dev/skills/aziontech/webkit/webkit-create-surface"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-create-surface/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-create-surface"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-create-surface.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.00169 | $0.02647 |
| Opus 5.5 | $0.00068 | $0.01059 |
| Sonnet 5.5 | $0.00034 | $0.00529 |
| Haiku 4.5 | $0.00017 | $0.00265 |
Grade A, and why
webkit-create-surface 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-create-surface
Purpose
"Where does this form go?" gets asked once per module and answered differently every time. One team ships a create page, the next ships a modal for the same shape of task, a third puts an inline row in the table — and the product teaches the reader three habits for one action. The cost is not aesthetic: a modal cannot be linked or reloaded, a page thrown up over a list destroys the context the reader was working in, and a dialog that holds a nine-field form traps them in a box they cannot resize.
This skill removes the question. The surface is a property of what is being created, not a choice the module makes. Three rules decide it, and one anatomy is shared by all of them so a reader who has created one resource recognizes every other.
1. The surface rule
A first-level resource creates on a PAGE. Anything created inside a resource opens a DRAWER. Nothing creates in a dialog.
First level means a resource the primary navigation routes to directly — the things the sidebar
lists. Creating one is the whole task: the reader came to do it, nothing behind it needs to stay
visible, and the result is something they will link to, reload and share. So it gets its own URL
(/<module>/new), its own screen, no sidebar, and it survives a refresh and the back button.
Inside a resource means a thing that only exists in the context of another: a record in a zone, a rule in an application, a column in a table, a domain on a workload. Creating one is a step in work already underway. The list behind the drawer is the context, and it has to stay visible — the thing being added is judged against the things already there. A page here would throw that away and make the reader navigate back to it.
Dialogs never create. A dialog is for a short blocking decision with one answer — a confirmation, a destructive guard. The moment it holds a form, it is a drawer with worse ergonomics: no resize, no scroll room, and a stray Escape destroys typed work.
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 · 192 lines · 169 tokens per session scan A d7b9ea92764f
webkit-create-surface is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 169 tokens to every session and 2,647 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-component
Design a UI component spec to the house quality bar — anatomy, variants, sizes, the 8 states, token mapping, and accessibility. Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework…
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…
design-screen
Design or build a page, screen, landing page, website, app or UI from a request - the whole job, end to end. Use this for "design a landing page", "build a settings screen", "make me a website", "design the onboarding", "ออกแบบหน้าเว็บ", "ทำหน้า landing", "ออกแบบ UI", "ทำแอป". It runs the pipeline no single skill…
grill-me
Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
scaffold-project
Scaffold a new design-product project that matches the recommended Claude Code layout (the reference structure). Use when starting a fresh product/app that will be built with this design system.