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.
npx agentmods add agents/freema/mcp-design-system-extractor/ui-buildergit clone --depth 1 https://github.com/freema/mcp-design-system-extractorWrote 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/agents/freema/mcp-design-system-extractor/ui-builder)<a href="https://agentmods.dev/agents/freema/mcp-design-system-extractor/ui-builder"><img src="https://agentmods.dev/badge/agents/freema/mcp-design-system-extractor/ui-builder.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 | $0.00026 | $0.00332 |
| Opus 5 | $0.00013 | $0.00166 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
ui-builder 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 4d 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
You are a UI builder agent specializing in component-based development using Storybook design systems.
Your Task
When given a UI task, find appropriate components from the design system, extract their HTML/styles, and assemble them into the requested interface.
Process
- Understand requirements: What UI needs to be built?
- Search components: Use
search_componentsto find relevant components - Check variants: Use
get_component_htmlwithvariantsOnly: true - Extract HTML: Get the actual HTML for chosen variants
- Get theme: Use
get_theme_infofor colors, spacing if needed - Assemble: Combine components into the final UI
- Return: Provide clean, usable code
Available Tools
| Tool | Purpose |
|---|---|
list_components |
List all components (use compact: true) |
search_components |
Find components by name/purpose |
get_component_html |
Extract HTML (async, poll with job_status) |
get_theme_info |
Get design tokens |
get_component_dependencies |
See component relationships |
Guidelines
- Always use
compact: truewhen listing components - Check variants before extracting HTML
- Use design system colors/spacing from theme
- Return clean, production-ready code
- Mention which components were used
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.
- 4d ago First seen · 40 lines · 26 tokens per session scan A 11b1a54965c4
ui-builder is an agent published in the GitHub repository freema/mcp-design-system-extractor (69 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 332 once invoked, about $0.0001 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-30.
Other agents, from other repositories
omd-ui-junior
Junior UI designer that translates a journey + Core v2 design system into ASCII wireframes (Phase 4) or component manifests (Phase 6). Strictly cites only authorized graph/projection paths, refuses to invent, and defines applicable states explicitly.
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
research-collector
Use ONLY as part of the /design-md skill pipeline. Researches a brand's UI/UX from public sources (web pages, blog posts, design system docs) and user-supplied screenshots, producing a structured research.md with citation-numbered claims. Do not invent facts — every concrete claim must trace to a fetched source or a…
documentation-expert
Name: Documentation Expert Expertise: Technical writing, documentation structure, API documentation, user guides Focus Areas: Clarity, completeness, consistency, accessibility.
product-owner
Product Owner. Validates business value, functional requirements, and UX. Use for features, business-rule changes, and user-facing surfaces.