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/battle)<a href="https://agentmods.dev/commands/manavarya09/design-extract/battle"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/battle/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/battle"><img src="https://agentmods.dev/badge/commands/manavarya09/design-extract/battle.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.00020 | $0.00255 |
| Opus 5.5 | $0.00008 | $0.00102 |
| Sonnet 5.5 | $0.00004 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
battle 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
Pit two sites against each other and emit a single shareable HTML battle card.
npx designlang battle $ARGUMENTS
If $ARGUMENTS is empty or contains fewer than two URLs, ask the user for both sites.
Both sites are extracted in parallel (~30s total). Outputs land in ./design-extract-output/:
<a>-vs-<b>.battle.html— the shareable card<a>-vs-<b>.battle.md— markdown summary<a>-vs-<b>.battle.json— structured scores
After the run:
- Read the
*.battle.mdfile - Show the user the verdict line ("X wins" / "tie") and the per-dimension table
- Highlight the dimensions where the gap is widest
- Offer to open the HTML card
This is pure viral content — battles are designed to be tweeted. Pair with /grade <url> --badge so each side has a permanent badge to link back to.
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 · 28 lines · 20 tokens per session scan A d961e9509eef
battle is a command published in the GitHub repository Manavarya09/design-extract (4,268 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 255 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.
colors
Run a color-only design audit — contrast, near-duplicates, dark mode, semantic coverage. 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.
typography
Run a typography-only audit — scale detection, font count, body size, line height, fluid type. Scoped variant of /ui-ux-suite:audit.
naksha-help
Quick-reference for any Naksha command — browse by category or look up a specific command.