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-listsgit 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-lists)<a href="https://agentmods.dev/skills/aziontech/webkit/webkit-lists"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-lists/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-lists"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/webkit-lists.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.05476 |
| Opus 5.5 | $0.00000 | $0.02190 |
| Sonnet 5.5 | $0.00000 | $0.01095 |
| Haiku 4.5 | $0.00000 | $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 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 — 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.
- 1mo ago First seen · 439 lines · 0 tokens per session scan A 9c3b9d3083f0
webkit-lists 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 5,476 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.