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/skills/validate-component/SKILL.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/skills/aziontech/webkit/validate-component)<a href="https://agentmods.dev/skills/aziontech/webkit/validate-component"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/validate-component/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/skills/aziontech/webkit/validate-component"><img src="https://agentmods.dev/badge/skills/aziontech/webkit/validate-component.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.00036 | $0.00677 |
| Opus 5.5 | $0.00014 | $0.00271 |
| Sonnet 5.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 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.
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.
- 2mo ago First seen · 70 lines · 36 tokens per session scan A cfdff66cdb57
validate-component is a skill published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 677 once invoked, about $0.0001 per session on Opus 5.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
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
design-qa
Set up or run design QA gates for token + hardcoded-value lint, automated a11y (axe), contrast, visual regression across variants/states/themes/RTL, and the manual a11y checklist. Use when the user wants CI quality gates, to prevent design regressions, or to QA a component/screen before shipping.
gate
Run the one-command quality gate and report the real N/N result. Use before claiming any build/review is done.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.
swarmauri-add-community-standalone
Add a second-class standalone Swarmauri package under pkgs/community. Use when Codex needs community package scaffolding, workspace membership, pyproject metadata, README branding, entry points, second-class citizenship rows, exports, tests, and validation.