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-usagenpx skills add aziontech/webkit --skill webkit-usagegit 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.00063 | $0.01357 |
| Opus 5 | $0.00032 | $0.00678 |
| Sonnet 5 | $0.00013 | $0.00271 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
webkit-usage 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-usage
Overview
@aziontech/webkit is the Azion design system: a set of themed, accessible Vue 3 components. This project depends on it. When you build or review UI here, reach for a webkit component first, import it with the flat path, and style with @aziontech/theme tokens. This skill is the paste-safe reference for doing that right.
How to find a component
Do not guess a component name or import path. Look it up.
- Ask the webkit MCP. The server exposes tools grounded in the exact webkit version this project installed:
suggest_component— describe what you need in plain words; it returns the matching component(s).- Import/validation tools — confirm a subpath is real and get the canonical path.
- Read the catalog directly.
node_modules/@aziontech/webkit/catalog.jsonhas animportsobject; every key is a real published subpath (button,empty-state,table, ...). If a subpath is not a key there, it does not exist.
App-level setup (setup in the catalog)
A few components need one-time wiring in the app entry before first use — the catalog entry (and get_component on the MCP) carries it in a setup field. When setup is non-null, apply it BEFORE emitting code that uses the component, and check whether the project already has it (do not duplicate).
- Toast: fire-from-anywhere (
toast.success('Saved')) only renders if a region is mounted. Wire the service once in the entry —import { ToastPlugin } from '@aziontech/webkit/toast'and chain.use(ToastPlugin)ontocreateApp(); the plugin mounts the region automatically (options:app.use(ToastPlugin, { position: 'top-right' })). A manually mounted Toaster also counts — never add both blindly (the store keeps only the first region active, but one wiring is enough).npx webkit doctorflags toast usage with no wired region.
Must Have
- ✅ Flat import:
import Button from '@aziontech/webkit/button'. - ✅ PascalCase binding matching the last path segment:
@aziontech/webkit/mini-button->MiniButton. - ✅ Color, spacing, radius, and typography from
@aziontech/themetokens (var(--primary),var(--spacing-md),text-button-lg). - ✅
import '@aziontech/theme'andimport '@aziontech/icons'once near the app entry (e.g.src/main.ts). - ✅ The tree-shakeable
<name>-rootpath (or specific sub-components) when you only need the root. - ✅ Icons via the
@aziontech/iconsfont: side-effect import once (import '@aziontech/icons') + the icon CSS classes. - ✅ A webkit component reused instead of a hand-rolled or third-party equivalent.
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 · 102 lines · 63 tokens per session scan A 207cc47fccb0
webkit-usage is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 1,357 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…