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/validate-componentnpx skills add aziontech/webkit --skill validate-componentgit 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.00036 | $0.00677 |
| Opus 5 | $0.00018 | $0.00338 |
| Sonnet 5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
validate-component 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: validate-component
Purpose
Confirm the scaffolded component compiles, lints, types, and builds. Surfaces failures to the orchestrator so the run can be marked degraded or rolled back.
When to invoke
- Step 8 of
/component-create, afterecho-reporterconfirmed parity.
Inputs
- The list of files written this run (from the orchestrator's run log).
- No mutation of the codebase.
Workflow
Run the four checks in this fixed order; stop on the first failure and surface it:
| # | Command | Failure means |
|---|---|---|
| 1 | pnpm webkit:lint |
ESLint reports an error or warning that crosses the project threshold. |
| 2 | pnpm webkit:type-check |
vue-tsc reports a TypeScript error in the component, its sub-components, or the consuming exports. |
| 3 | pnpm webkit:type-coverage |
Type coverage below the threshold (project default: 95%). |
| 4 | pnpm storybook:build |
The new .stories.js breaks the Storybook build. |
For each command, capture the exit code and the last 40 lines of stdout/stderr. Emit a table:
| Check | Result | Detail |
|---|---|---|
| `pnpm webkit:lint` | ✅ pass | 0 warnings |
| `pnpm webkit:type-check` | ✅ pass | — |
| `pnpm webkit:type-coverage` | ✅ pass | 97.2% (threshold 95%) |
| `pnpm storybook:build` | ✅ pass | build output OK |
If any row is ❌, include the last 40 lines of the tool's output below the table and stop.
Outputs
- The Markdown table above + (on failure) the tail of the failing command's output.
Rules
- Do not auto-fix lint failures. Surface them and stop — the user (or a follow-up sub-agent) decides whether to fix.
- Do not run
pnpm install. If a dep is missing, surface that as the failure reason. - Do not run
git. Validation never touches the working tree.
Fallbacks
- A script is missing from
package.json→ emitBLOCKED: script <name> not found in root package.json. - A command hangs > 5 min → emit
BLOCKED: <command> timed outand exit.
Definition of Done
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 · 70 lines · 36 tokens per session scan A cfdff66cdb57
validate-component is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 677 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 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…