design-extract is a command-line tool that examines live websites with a headless browser and turns their visual and interaction rules into design-system files. It is used by developers and designers to extract tokens, component details, responsive behavior, accessibility findings, and platform-specific outputs, while the catalogue commands, skills, plugin, and rule expose that process to coding agents.
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.
git clone --depth 1 https://github.com/Manavarya09/design-extractWrote 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/manavarya09/design-extract/verify)<a href="https://agentmods.dev/commands/manavarya09/design-extract/verify"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/verify/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/manavarya09/design-extract/verify"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/verify.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.00031 | $0.00312 |
| Opus 5.5 | $0.00012 | $0.00125 |
| Sonnet 5.5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
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 1mo 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.
What it actually says
Run designlang verify to close the extraction loop. It rebuilds a page from the extracted design tokens, renders it, pixel-diffs that render against the live site, and reports a fidelity score — how faithfully the tokens reproduce the real design.
npx designlang verify $ARGUMENTS
If no $ARGUMENTS were supplied, ask the user which URL to verify.
After the run completes, surface the fidelity score and the biggest divergences (where the rebuilt page drifts from the live site). This is the honest "did we actually capture it?" signal.
Useful flags via $ARGUMENTS:
| Flag | Effect |
|---|---|
--min <score> |
exit non-zero if fidelity is below this (CI gate) |
--tokens <file> |
verify against a local tokens file (.json or .css) instead of a fresh extraction |
Use --min in CI to fail a build when a design change drops fidelity below a
threshold. Pair with /site <url> to verify the whole-site canonical system.
Full reference: https://github.com/Manavarya09/design-extract#full-cli-reference
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.
- 1mo ago First seen · 32 lines · 31 tokens per session scan A e630b0620c42
verify is a command published in the GitHub repository Manavarya09/design-extract (4,257 stars, last pushed 10d ago), licensed MIT. It adds 31 tokens to every session and 312 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-30.
Other commands, from other repositories
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
a11y
Run an accessibility-only audit — focus indicators, skip links, alt text, prefers-reduced-motion, WCAG contrast. Scoped variant of /ui-ux-suite:audit.
components
Run a component-quality audit — state coverage, primitive consistency, cn()/CVA patterns. Scoped variant of /ui-ux-suite:audit.
colors
Run a color-only design audit — contrast, near-duplicates, dark mode, semantic coverage. Scoped variant of /ui-ux-suite:audit.
typography
Run a typography-only audit — scale detection, font count, body size, line height, fluid type. Scoped variant of /ui-ux-suite:audit.
dashboard-layout
Design and build a complete dashboard layout — sidebar navigation, KPI cards, chart areas, data tables, filter bar, and responsive behavior. Outputs production-ready HTML/CSS.