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/pack)<a href="https://agentmods.dev/commands/manavarya09/design-extract/pack"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/pack/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/pack"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/pack.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.00405 |
| Opus 5.5 | $0.00017 | $0.00162 |
| Sonnet 5.5 | $0.00009 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
pack 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 the full extraction once and write every emitter output into a single, signed, layered directory.
npx designlang pack $ARGUMENTS
If no URL is provided, ask the user. Default output is ./<host>-design-system/.
Layout produced:
<host>-design-system/
├── README.md bespoke "Built from <host>" + grade + at-a-glance
├── LICENSE.txt provenance + usage guidance
├── tokens/ DTCG + Tailwind + CSS vars + Figma vars + motion + theme.js
├── components/ typed React stubs (anatomy.tsx)
├── storybook/ runnable Storybook project
├── starter/ minimal HTML starter wired to tokens/variables.css
├── prompts/ v0 / Lovable / Cursor / Claude Artifacts + named recipes/*.md
└── extras/ voice.json + prompt-pack.md rollup
After the run:
- Surface the headline (
X files, Y KB · ./<dir>) - Read the auto-generated
README.mdand tell the user what's inside - Suggest next steps:
cd <dir> && zip -r ../<dir>.zip .to package for sharingcd <dir>/storybook && npm install && npm run storybookto run the design system locally- Copy
tokens/tailwind.config.jsstraight into a project
Use --with-clone to swap the minimal HTML starter for the full Next.js clone (slower; only when the user wants a runnable app).
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 · 38 lines · 43 tokens per session scan A af4001f0ba79
pack is a command published in the GitHub repository Manavarya09/design-extract (4,257 stars, last pushed 10d ago), licensed MIT. It adds 43 tokens to every session and 405 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-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.