agentmods.dev

component-verify

A read-only verification command for an existing Vue component, checking its specification, checksum, generated output, and project validation results.

In plain words
What is it for?
Use it to verify a named component after editing. It checks specification compliance, file parity, linting, types, type coverage, declaration output, and the Storybook build.
Why use it?
It detects when the component or its specification has drifted from the expected version without modifying either one.

Command for Claude Code

2 3d ago A scan 30 tokens original MIT
View the source file aziontech/webkit
Install

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.

agentmods
npx agentmods add commands/aziontech/webkit/component-verify
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code.

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 392 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.00392
Opus 5 $0.00015 $0.00196
Sonnet 5 $0.00006 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured yesterday against content hash c4f5a93a14b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

component-verify 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.

.claude/commands/component-verify.md · 25 lines

What it actually says

You are running /component-verify <name>. You do not write anything. You re-execute the read-only phases of /component-create against an existing component.

User input: $ARGUMENTS

What to do

  1. Resolve .specs/<name>.md. If absent → exit with the path it expected.
  2. Run spec-validator on the current spec content. Surface any failures.
  3. Recompute sha256(body) and compare to frontmatter checksum. Mismatch → surface and exit.
  4. Resolve the existing component dir at packages/webkit/src/components/webkit/<category>/<name>/. Missing → exit.
  5. Spawn echo-reporter against the disk files. Surface its verdict (parity / mismatch / degraded).
  6. Spawn validate-component (pnpm webkit:lint, type-check, type-coverage, dts build, storybook build).
  7. Print a one-table summary: spec status, hook verdict, echo verdict, validation pass/fail.

Rules

  • Read-only. This command writes nothing — no specs, no .vue, no logs (other than a one-line summary in .claude/logs/<run-id>.jsonl).
  • No retries on failure. Surface and exit. The user fixes the divergence (in the spec or in the .vue) and re-runs.
  • No sub-agent spawned that writes. Forbidden: scaffolder, storybook-writer, code-connect-writer, spec-author, spec-validator (which writes the checksum — exception: run it in dry-mode where it returns the verdict without flipping status).
Changes

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.

  1. yesterday First seen · 25 lines · 30 tokens per session scan A c4f5a93a14b7

Subscribe to this mod's changes

component-verify is a command published in the GitHub repository aziontech/webkit (2 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 392 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.

FrontendTestingWriting and docscomponent-libraryfrontend-platformmonorepoui-architectureworkspace
Related

Other commands, from other repositories

speckit.tasks

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

Weaverse/weaverse · 18 tokens

speckit.implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

Weaverse/weaverse · 14 tokens

diagnose

Run sivtr doctor to check the environment, then investigate any failing checks.

Ariestar/sivtr · 0 tokens

test-changed

Run the full quality gate on only the files changed since branching from main.

Ariestar/sivtr · 0 tokens

route

Route notes from inbox to appropriate vault destinations.

technicalpickles/pickled-claude-plugins · 8 tokens

cleanup-transcript

Clean up a video/audio transcript (SRT or plaintext) - identifies structure, fixes transcription errors, asks clarifying questions iteratively.

technicalpickles/pickled-claude-plugins · 26 tokens