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-data-viznpx skills add aziontech/webkit --skill webkit-data-vizgit 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.00114 | $0.02385 |
| Opus 5 | $0.00057 | $0.01192 |
| Sonnet 5 | $0.00023 | $0.00477 |
| Haiku 4.5 | $0.00011 | $0.00238 |
Grade A, and why
webkit-data-viz 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: webkit-data-viz
Purpose
A chart muddy in one theme, or spinning forever on an empty dataset, is broken the same way a
mis-tokened button is — and Azion Console is an observability product, so charts are a primary
surface, not decoration. This skill is the token adapter: it takes the charting decisions and
realizes them in @aziontech/theme. For chart-form (which form answers which question) and palette
theory (categorical / sequential / diverging, contrast math, color-blind pairing), see the generic
dataviz skill; this skill covers only mapping that onto @aziontech/theme tokens — deriving every
color from the --color-* families (never hex), re-reading computed tokens on a data-theme change so
a canvas re-themes (SVG re-themes for free), and rendering the chart's loading / empty / error surface
with webkit components. It does not pick your charting library — canvas or SVG rendering is a
consumer choice; the tokens below are not.
How to use
/webkit-data-viz— apply the token mapping to any chart, dashboard, or KPI tile you build in this conversation. Pick the form and the palette kind with the genericdatavizskill first, then map it onto tokens here./webkit-data-viz <file>— review the file's charts and report, per gap: the quoted line, the token problem (off-token color, no theme re-read, missing state, non-tabular figures), and the concrete token-mapped fix. Form and palette-kind review belong to the genericdatavizskill.
How to find the components + tokens
Never guess an import path or a hex value. Resolve both from the contract:
- Components (
Skeleton,EmptyState,Message,CardBox,StatusIndicator): ask the webkit MCP —suggest_componentin plain words ("empty state", "stat card") — or read theimportskeys innode_modules/@aziontech/webkit/catalog.json. A subpath that is not a key there does not exist. - Tokens: read the
tokenstree in the samecatalog.json(the--color-*families:blue,violet,green,orange,yellow,red, each50→950; plus--success,--warning,--danger,--info), or the human catalog innode_modules/@aziontech/webkit/docs/STYLEGUIDE.md. Derive every chart color from these — never a raw hex.
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 · 178 lines · 114 tokens per session scan A b3949e791807
webkit-data-viz is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 114 tokens to every session and 2,385 once invoked, about $0.0006 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-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…
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/.