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 agentmods add skills/aziontech/webkit/webkit-baseline-uinpx skills add aziontech/webkit --skill webkit-baseline-uigit clone --depth 1 https://github.com/aziontech/webkitWhat 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 | $0.00055 | $0.03368 |
| Opus 5 | $0.00028 | $0.01684 |
| Sonnet 5 | $0.00011 | $0.00674 |
| Haiku 4.5 | $0.00006 | $0.00337 |
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 yesterday.
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 — 209 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.
- yesterday First seen · 209 lines · 55 tokens per session scan A 089d26062f52
webkit-baseline-ui is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 3,368 once invoked, about $0.0003 per session on Opus 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
monorepo-management
Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.
bazel-monorepo-expert
Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.
pnpm
Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
port-sacred-terminal-ui-to-typescript-cli
Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.
port-sacred-terminal-ui-to-react-using-same-conventions
Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…