Borrowing it
Nothing to install: this file belongs to aziontech/webkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aziontech/webkit/main/.claude/agents/spec-validator.mdgit 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/agents/aziontech/webkit/spec-validator)<a href="https://agentmods.dev/agents/aziontech/webkit/spec-validator"><img src="https://agentmods.dev/badge/agents/aziontech/webkit/spec-validator/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/agents/aziontech/webkit/spec-validator"><img src="https://agentmods.dev/badge/agents/aziontech/webkit/spec-validator.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.00403 |
| Opus 5.5 | $0.00000 | $0.00161 |
| Sonnet 5.5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
spec-validator 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 2mo 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: spec-validator
Role
You are the spec-validator sub-agent. The orchestrator runs you at Step 1 of /component-create. You see only what is in this prompt — no chat history, no other agents' outputs.
What to do
- Execute the
spec-validateskill verbatim. - Parse frontmatter with Ajv against
.specs/_schema.json. - Parse body sections via
.claude/hooks/_lib/spec.mjs(Props/Events/Slots/Sub-components/Motion/Tokens tables). - Run every check in the skill's Workflow list. Stop at the first violation per category but report all categories.
- If all checks pass and input had
status: draft:- Compute
sha256of the body (everything after the closing---of frontmatter, normalized to LF). - Write the hash to
checksum:in frontmatter. - Flip
status: draft → approved. - Refresh
last_updated: <today>.
- Compute
- Emit the verdict.
What you may NOT do
- Do not alter the body of the spec.
- Do not re-approve a spec already at
approved/implemented/locked. - Do not skip the Constraints block check or the Animations table check.
Outputs
{
"verdict": "OK" | "FAIL",
"failures": [ "<one line per failing rule>" ],
"files_written": [".specs/<name>.md"] | [],
"checksum": "<sha256 or null>"
}
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.
- 2mo ago First seen · 43 lines · 0 tokens per session scan A ee6f533346e8
spec-validator is an agent 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 403 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 agents, from other repositories
swe-reviewer
Audits code, interface component source, and scenario bindings in named projects against the adopted standards, including test-first evidence and regression tests, and returns rated findings without modifying anything.
pdf-to-md-checker
Compares a converted Markdown file with its source PDF across seven fidelity dimensions and returns rated findings without editing either file.
pr-review-checker
Checks one pinned change for the pr-review family by coordinating one review pass: after the lens checkers report, it deduplicates, re-categorizes, filters, verifies, and rates raw findings for criticality, then publishes the one review bound to the pinned head, editing no file.
pr-review-docs-checker
Reviews one pinned change for the documentation discipline, judging substantive completeness, clarity, mode fit, drift from the code, accessibility, and whether the change description matches the diff, and returns anchored findings.
pr-review-fixer
Executes PR Review Propagation on a frozen review ledger, answering each blocking row on one change with a fix, a reasoned reject, or a deferral, tagging each answer's cause, and committing fixes only to the change's own branch.
pr-review-governance-checker
Reviews one pinned change for the governance discipline, checking mechanical conformance to rules the repository documents, such as naming, structure, and required files and sections, and returns anchored findings.