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-navigationgit 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-navigation)<a href="https://agentmods.dev/skills/aziontech/webkit/webkit-navigation"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-navigation/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-navigation"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-navigation.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.00000 | $0.08143 |
| Opus 5.5 | $0.00000 | $0.03257 |
| Sonnet 5.5 | $0.00000 | $0.01629 |
| Haiku 4.5 | $0.00000 | $0.00814 |
Grade A, and why
webkit-navigation 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 — 631 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-navigation
Purpose
Every screen in a console lives in one of two navigation shells, and picking the wrong one — or
worse, blending them — is where a prototype stops feeling like one product. A browse page with no way
back to the rest of the console strands the user; a focused create flow that keeps the full sidebar
lets the user wander off mid-task and lose their work. This skill fixes which shell a page uses, how
each is composed on @aziontech/webkit, and the one invariant they share: the signed-in user is
always visible. It is the layout-shell companion to webkit-form (what goes inside a focused
flow) and webkit-ux-heuristics (states + feedback).
How to use
/webkit-navigationApply the shell rules below to any page or flow you build in this conversation./webkit-navigation <file>Review the file against the rules and output, per gap:- the exact line / element (quoted),
- which rule it breaks (1 short sentence),
- the concrete fix, naming the shell or webkit primitive to use.
When to invoke
- Starting a new page and deciding how it sits in the app (a hub page vs a create/edit/deploy flow).
- The user asks "which header goes here", "should this have a sidebar", "how do I get back", "the user disappeared on the create screen".
- Reviewing a screen for whether it uses the right shell and shows exactly one header.
How to find the components
Never guess an import path, and never copy one from another repo or sample app — files move. Resolve every webkit primitive the same way:
- Ask the webkit MCP —
suggest_componentin plain words ("sidebar", "app header", "breadcrumb"). - Or read
node_modules/@aziontech/webkit/catalog.json— every key underimportsis a real published subpath. If a subpath is not a key there, it does not exist.
The primitives you compose the shells from — sidebar (+ sidebar-header, sidebar-group,
sidebar-footer), global-header, breadcrumb, tab-view — all resolve this way. There is no
@aziontech/webkit/app-layout and no @aziontech/webkit/creation-header: the two shells are
components you compose in your own app (shown below), not webkit imports — never copy a dead import
for them.
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 · 631 lines · 0 tokens per session scan A bd4cf4efe96f
webkit-navigation is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 8,143 tokens. 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.