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/commands/component-create.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/commands/aziontech/webkit/component-create)<a href="https://agentmods.dev/commands/aziontech/webkit/component-create"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/component-create/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/commands/aziontech/webkit/component-create"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/component-create.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.00043 | $0.01343 |
| Opus 5.5 | $0.00017 | $0.00537 |
| Sonnet 5.5 | $0.00009 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
component-create 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the orchestrator for /component-create. You do not write component code yourself. You execute a fixed pipeline that delegates each phase to an isolated sub-agent. Each sub-agent receives only the spec + its narrow rules — never the conversation, never another sub-agent's output (except sanitized JSON artifacts you explicitly pass forward).
User input: $ARGUMENTS
Pipeline
Step 0 — Preflight
- Parse
<name>. Reject if missing/invalid.--dry-runruns Steps 0–3 and exits with a preview (no writes). - Generate a run-id (uuid). Open
.claude/logs/<run-id>.jsonland append one line per phase. - Resolve
.specs/<name>.md:- Absent → tell the user
Run /spec-create <name> first.Exit 1. status: draft→ tell the user the spec is not approved; suggest re-running after fixing issues. Exit 1.status ∈ {approved, implemented}→ proceed (implemented re-runs are allowed for follow-up edits).status: locked→ block unless the user explicitly bumpsspec_version. Exit 1.
- Absent → tell the user
- Recompute
sha256(body)and compare to the frontmatterchecksum. Mismatch →BLOCKED: spec tampered after approval. Exit 1.
Step 1 — Spec validation (blocking)
Spawn the spec-validator sub-agent with the universal envelope (see .claude/agents/_README.md). It re-runs the schema, body, and Constraints checks. On FAIL, surface every failure and exit. No writes happen until this passes.
Step 2 — Parallel discovery (read-only, safe to parallelize)
figma-extractor(only ifspec.figma.urlis set) — emits tokens JSON.reuse-auditor— emits reuse JSON.- After
figma-extractorreturns, runtoken-mapperon its output — emits mapping + theme gaps.
Step 3 — Reconciliation (blocking)
- Every token listed in
spec.Tokensmust resolve intoken-mapperoutput (no theme gaps that the spec did not flag). - Every region from
figma-extractormust be covered by the spec (Props/Slots/Sub-components). - Mismatch → exit with the diff and instruct the user to update the spec and re-run.
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 · 78 lines · 43 tokens per session scan A 1e622326e771
component-create is a command published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,343 once invoked, about $0.0002 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 commands, from other repositories
init-workspace-flow-questions
Phase 8 Questions of init-workspace-flow.
security
Scan application source, agent skills or MCP components; run scoped web test penetration tests, validate findings and configure security gates through oma-security.
design
Design workflow that creates design systems, DESIGN.md, and design tokens with anti-pattern enforcement and accessibility checks.
tools
Manage MCP tools with natural language commands to list, enable, and disable tools and tool groups.
setup
Interactive setup for Vue.js LSP development environment.
svelte:storybook-troubleshoot
Diagnose and fix common Storybook issues in SvelteKit projects, including build errors, module problems, and configuration issues.