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-listsnpx skills add aziontech/webkit --skill webkit-listsgit 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.00215 | $0.05476 |
| Opus 5 | $0.00108 | $0.02738 |
| Sonnet 5 | $0.00043 | $0.01095 |
| Haiku 4.5 | $0.00021 | $0.00548 |
Grade A, and why
webkit-lists 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-lists
Purpose
A product's list pages are the screens people spend the most time on and the ones that drift the fastest.
Each one is built by whoever needed it, so one index puts a row of Selects above the table, the next hides
the same job behind a badged funnel button, a third uses an operator builder with a contains dropdown
nobody changes from the default — and none of them agree on where the search field goes or how much air
sits between the controls and the rows they narrow.
They are all the same page. This skill fixes that page: one skeleton, one filter model, and one
rule for which columns become filters. /webkit-tables owns what happens inside the Table — the
column model, the toolbar, the cell recipes. This skill owns everything around it: the page's structure,
the controls row, the filter bar, and the state that connects them.
Find the components named here through the webkit MCP (suggest_component / get_component) or
node_modules/@aziontech/webkit/catalog.json.
How to use
/webkit-lists— build any index page in this conversation to the shape below./webkit-lists <file>— review that page against the patterns; per gap report the exact line/element (quoted), which pattern it breaks (one sentence), and the concrete fix.
Related: /webkit-tables (the Table, columns, cells) · /webkit-navigation (the app shell the page sits
in) · /webkit-ui-states (the empty and loading states a filtered list must render) ·
/webkit-microcopy (field labels, the empty-state sentence).
When to invoke
- Building any "all X" / resource index / management list page.
- Adding filtering to an existing table, or being asked "how do I filter this".
- Reviewing a page whose controls row has grown a third
Select. - The user says the filters look different from the other pages, the table jumps to an empty page after filtering, or the search and the filters fight each other.
1. The list page, one shape
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 · 439 lines · 0 tokens per session scan A 9c3b9d3083f0
webkit-lists is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 215 tokens to every session and 5,476 once invoked, about $0.0011 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…