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/spec-validatenpx skills add aziontech/webkit --skill spec-validategit 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.00041 | $0.01083 |
| Opus 5 | $0.00020 | $0.00541 |
| Sonnet 5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
spec-validate 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: spec-validate
Purpose
Decide whether a spec is good enough to drive code generation. The spec-validator sub-agent runs this skill at Step 1 of /component-create. Validation must be deterministic — same spec, same verdict.
When to invoke
- Step 1 of
/component-create <name>(orchestrator passes the spec content). /component-verify <name>(manual re-check).- Hook test suite (against
.specs/__fixtures__/*).
Inputs
- The full text of
.specs/<name>.md(frontmatter + body). .specs/_schema.json(frontmatter schema)..claude/docs/DESIGN.md(to verify Token references).
Workflow
- Parse frontmatter. Run Ajv against
_schema.json. Any violation → fail with the Ajv error path. - Parse body sections. Use
.claude/hooks/_lib/spec.mjsto extract the Props / Events / Slots / Sub-components / Tokens tables. Fail if any mandatory section is absent or contains onlyTBD. - Check Props table. Each row must have all five cells filled. Boolean prop names must not start with
is/has. Visual variant prop must be namedkind. Size prop must be namedsize. JSDoc cell must not be empty. The Default cell must NOT be the string literal'undefined'or'null'(the quoted text, not the JS valueundefined): for an optional text prop use'', for a genuinely absence-meaningful prop (open,modelValue,src) use unquotedundefined. Fail withFAIL: prop <name> Default is the string 'undefined'; use '' or unquoted undefined(helper:defaultCellIsStringUndefinedin.claude/hooks/_lib/spec.mjs). - Check Events table. Event names must be kebab-case OR
update:<prop>. Payloads must be a TypeScript type (noany, no empty). - Check Slots table. Slot names must be kebab-case. Scope must be
—or a typed object. - Check Sub-components. If
structure: composition, the Sub-components section must list at least the root + one sub-component. Ifstructure: monolithic, the section must be absent. - Check Tokens. Every "Token (DESIGN.md)" cell must match one of:
- A generated class starting with
.text-and present in DESIGN.md. - A
var(--*)that exists in DESIGN.md. No HEX, no RGB, no Tailwind palette, no external color utility.
- A generated class starting with
- Check Constraints block. The "## Constraints — DO NOT" section must be present and must contain at least the bullets from
.specs/_template.md(verbatim text check on the canonical bullets). - Write checksum. If all checks pass and the input had
status: draft, computesha256(body)(everything after the closing---of the frontmatter), write it to thechecksumfield, and flipstatus: approved. Refreshlast_updated. - Emit verdict. Print
OKor a list of failures (one per line, with the failing line number).
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 · 68 lines · 41 tokens per session scan A 3f52a2ebb262
spec-validate is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 1,083 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…