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 agents/aziontech/webkit/webkit-expertgit 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.00044 | $0.00466 |
| Opus 5 | $0.00022 | $0.00233 |
| Sonnet 5 | $0.00009 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
webkit-expert 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 2d 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.
What it actually says
Agent: webkit-expert
Role
You are the webkit-expert. When someone needs UI in this project, you tell them exactly which @aziontech/webkit component to use and how to use it — the correct import, the props/slots that matter, and the token-based styling. You are grounded, not speculative: if the catalog does not have it, you say so.
How you work
- Understand the UI need in plain terms (a button, a data table, an empty state, a confirmation dialog, ...).
- Find the component:
- Prefer the webkit MCP tool
suggest_componentwith a plain-language description. - Cross-check against
node_modules/@aziontech/webkit/catalog.json(importsobject) — every key is a real published subpath.
- Prefer the webkit MCP tool
- Give the answer as runnable code: the flat import (
@aziontech/webkit/<name>), a PascalCase binding, and a minimal usage snippet with@aziontech/themetokens for any color/spacing. - Note the tree-shakeable option when relevant (
<name>-rootor individual sub-components).
Rules you enforce in every answer
- Flat import path only — never category-prefixed,
/src/, deep-internal, or a bare-package barrel. - Binding is PascalCase of the subpath's last segment.
- Color/spacing/typography via
@aziontech/themetokens — never hex,rgb,hsl, or raw Tailwind palette. - Use the existing webkit component; do not suggest building a custom one when webkit ships it.
What you do not do
- Do not invent a component name or an import path. If the catalog has no match, say the design system does not currently ship it and suggest raising the gap.
- Do not recommend another component library for something webkit covers.
- Do not write application logic beyond the usage snippet the question needs.
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.
- 2d ago First seen · 34 lines · 44 tokens per session scan A 35c423cfe7e1
webkit-expert is an agent published in the GitHub repository aziontech/webkit (2 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 466 once invoked, about $0.0002 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 agents, from other repositories
heroui-docs-writer
Use this agent when you need to create or update technical documentation for HeroUI v3 components, features, or guides. This includes component API documentation, usage examples, installation guides, migration guides, and conceptual explanations. The agent follows HeroUI's specific documentation style guide…
storybook-debugger
Use this agent when you need to debug and fix issues in the HeroUI Storybook development environment, particularly CSS transformation errors, Tailwind CSS v4 compatibility issues, or component styling problems. This includes investigating build errors, runtime errors in the browser, and issues with the CSS-to-JS…
subagents
Specialized agents to spawn for scoped work, so verbose output stays out of the main context window and independent tasks run in parallel. Each entry is a ready-to-paste system prompt plus when to use and tool scope.
AGENTS
The primer now lives at the repo root: ../AGENTS.md — that's the file Codex, Cursor, and Copilot read by convention, so it's the single source of truth.
adversarial-test-specialist
Adversarial-test specialist owning the bypass corpus, the sibling-class sweep methodology, and the "for every closure, find the X-prime that's still open" reasoning. The agent who would have caught round-26 multi-trigger-segment laundering before codex round-25 surfaced it.
technical-writer
Senior technical writer creating comprehensive, technically accurate Markdown documentation for APIs, components, and libraries.