What is verify-component?

A component-checking workflow for a specific component in the `@agentic-ds` codebase. It builds, checks code style, and runs unit tests for the component files that exist.

Use it after changing a component or as the final check when adding one. It can verify the component’s source, story, and tests, and reports the commands and output.

It limits verification to the changed component, so unrelated problems elsewhere do not obscure the result. It also identifies errors that need fixing instead of hiding them.

How brianmontanaweb/agentic-design-system configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to brianmontanaweb/agentic-design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/brianmontanaweb/agentic-design-system/main/.claude/skills/verify-component/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/brianmontanaweb/agentic-design-system

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/brianmontanaweb/agentic-design-system/verify-component/github.svg)](https://agentmods.dev/skills/brianmontanaweb/agentic-design-system/verify-component)

Your own site

<a href="https://agentmods.dev/skills/brianmontanaweb/agentic-design-system/verify-component"><img src="https://agentmods.dev/badge/skills/brianmontanaweb/agentic-design-system/verify-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/brianmontanaweb/agentic-design-system/verify-component"><img src="https://agentmods.dev/badge/skills/brianmontanaweb/agentic-design-system/verify-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 784 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00074	$0.00784
Opus 5.5	$0.00030	$0.00314
Sonnet 5.5	$0.00015	$0.00157
Haiku 4.5	$0.00007	$0.00078

Measured 2mo ago against content hash 4626354ce5da, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/skills/verify-component/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verify Component

Build, lint, and test one component given $ARGUMENTS in the format <ComponentName>.

Gotchas

Run npm run build before any lint — tsc --noEmit requires the tokens package to be built first.
Scope is this component's files only — pre-existing violations elsewhere in the repo are not your responsibility and must not block a passing report.
Fix, don't suppress — no eslint-disable comments; fix the underlying issue in the component's files.
Only verify files that exist — skip the story or test command (and say so) if that file hasn't been created yet; do not create missing files. Point to /add-component-story / /add-component-tests for gaps.

Step 1 — Resolve files

ls packages/core/src/<ComponentName>/<ComponentName>.tsx packages/agents/src/<ComponentName>/<ComponentName>.tsx 2>/dev/null

If no output, stop immediately and respond:

## No source: <ComponentName>

Neither package contains `<ComponentName>`. Create it first with
`/add-component-source <ComponentName>` (source only) or `/add-component <ComponentName>` (full scaffold).

Infer the package from which path exists, then check which of these also exist:

packages/<package>/src/<ComponentName>/<ComponentName>.test.tsx
apps/storybook/src/stories/<ComponentName>.stories.tsx

Step 2 — Build, lint, test

Run in order, skipping commands whose target file doesn't exist:

npm run build
eslint packages/<package>/src/<ComponentName>/<ComponentName>.tsx apps/storybook/src/stories/<ComponentName>.stories.tsx
npx vitest run packages/<package>/src/<ComponentName>/<ComponentName>.test.tsx

Fix any errors ESLint or vitest reports on this component's files, then re-run the failed command until it passes. If the build itself fails because of this component's files, fix and re-run; if it fails elsewhere in the repo, report it and stop — that is outside this skill's scope.

Also run the theme-safety check — components must support light/dark via semantic tokens only (see the Theming section of the shared conventions reference):

Read the full file on GitHub · 77 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

evals/evals.json 2.4 KB

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.

2mo ago First seen · 77 lines · 74 tokens per session scan A 4626354ce5da

Subscribe to this mod's changes

verify-component is a skill published in the GitHub repository brianmontanaweb/agentic-design-system (3 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 784 once invoked, about $0.0003 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.

Testing Unit testing accessibility agentic ai-agents chakra-ui component-library design-system

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.

plugin87/ux-ui-agent-skills · 37 tokens

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.

plugin87/ux-ui-agent-skills · 71 tokens

agentic-design-system: Skill for Claude Code