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.
curl -O https://raw.githubusercontent.com/brianmontanaweb/agentic-design-system/main/.claude/skills/verify-component/SKILL.mdgit clone --depth 1 https://github.com/brianmontanaweb/agentic-design-systemWrote 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/brianmontanaweb/agentic-design-system/verify-component)<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="Measured on agentmods" 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.00074 | $0.00784 |
| Opus 5 | $0.00037 | $0.00392 |
| Sonnet 5 | $0.00015 | $0.00157 |
| Haiku 4.5 | $0.00007 | $0.00078 |
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 7d 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 — 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 buildbefore any lint —tsc --noEmitrequires 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-disablecomments; 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-testsfor 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.tsxapps/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):
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.
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.
- 7d ago First seen · 77 lines · 74 tokens per session scan A 4626354ce5da
verify-component is a skill published in the GitHub repository brianmontanaweb/agentic-design-system (3 stars, last pushed 18d ago), licensed MIT. It adds 74 tokens to every session and 784 once invoked, about $0.0004 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.
Other skills, from other repositories
design-qa-checklist
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use handoff-spec.
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).
test-microflows
Write and run MDL-based microflow tests with mxcli test — annotations, file formats, and the warm local test loop. Use when testing microflow logic rather than the UI: return values, entity changes, control flow.
06-test
Write and iterate tests until they pass, or validate a user journey end to end in the browser. Use when the user wants to add coverage, find what's untested, or walk a flow. Not for auditing test health or debugging a failure.
validation-microflows
Validation microflows for new/edit pages — attribute checks, feedback messages, and conditional validation chains. Use when a form needs input validation with messages shown against the fields.
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…