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/plugins/manavarya09/design-extract/designlang)<a href="https://agentmods.dev/plugins/manavarya09/design-extract/designlang"><img src="https://agentmods.dev/badge/plugins/manavarya09/design-extract/designlang/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/plugins/manavarya09/design-extract/designlang"><img src="https://agentmods.dev/badge/plugins/manavarya09/design-extract/designlang.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
designlang 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 today.
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
{
"name": "designlang",
"source": "./",
"description": "Thirteen slash commands wrapping the designlang CLI: /extract (full design language → DTCG, Tailwind, Figma), /site (crawl a whole site → one canonical design system + consistency grade), /grade (shareable HTML report card + SVG badge), /battle (head-to-head graded comparison), /remix (restyle in 6 vocabularies — brutalist, swiss, art-deco, cyberpunk, soft-ui, editorial), /pack (one downloadable design-system bundle), /theme-swap (OKLCH-correct recolour around a new brand primary), /brand (full editorial brand-guidelines book — 13 chapters, hand-off-ready), /pair (fuse two designs across configurable axes — colours from one site, typography from another), /studio (live token-editor with component preview + export), /verify (rebuild from tokens and pixel-diff vs live for a fidelity score), /fidelity (score a clone vs the original — visual pixel-diff + motion fidelity — with a ranked correction plan), /gallery (build a shareable static gallery of measured clones).",
"version": "13.2.0",
"author": {
"name": "Manavarya Singh"
},
"category": "design",
"tags": [
"design-system",
"design-tokens",
"dtcg",
"tailwind",
"shadcn",
"figma",
"typography",
"colors",
"motion",
"grade",
"battle",
"remix",
"pack",
"site",
"studio",
"verify",
"mcp",
"playwright"
]
}What ships with it
2 files beside marketplace.json#designlang 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.
- today First seen · 30 lines scan A 56d7b812a786
designlang is a plugin published in the GitHub repository Manavarya09/design-extract (4,061 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-09.
Other plugins, from other repositories
uisandbox
Play with your app's design, right in the browser: open a built web app in UISandbox, 1:1 and with its own knobs, from the chat; try a change, verify, export the patch. Bundles the /uisandbox skill and the uisandbox MCP server.
design-system-ops
Staff-level design system auditing, governance, documentation, validation, and communication — 40 skills, 4 agents, and 12 knowledge notes for the full design system lifecycle.
roast-my-design-system
Roast your repo's design system with real data: a health score, the receipts behind it (every colour, spacing value, duplicated component and inline style), and the first fixes ranked by payoff. Deterministic scanner, benchmarked against 29 public repos and 10 reputable design systems, one shareable light/dark HTML…
google-fonts
Google Fonts typography system generator. Searches 1,923 fonts, suggests singles or pairs, generates CSS/Tailwind typographic systems.
ui-ux-suite
Design audit tool. Scores projects across 12 dimensions: color, typography, accessibility, layout, and more. WCAG, APCA, OKLCH color science. Zero dependencies.
ui-ux-design-pro
World-class, one-stop design intelligence for coding agents across two tracks: interfaces (web/apps, components, design systems, the modern React+Tailwind+shadcn stack) AND visual/marketing design (presentations & decks, social carousels & posts, ads, A4/A3 posters, flyers, business cards, event banners…