design-bridge

design-bridge is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 62 tokens per session (980 once invoked), scanned A, original, MIT.

A design-translation agent that turns a DESIGN.md document into practical instructions for building a matching user interface. DESIGN.md is a written description of a product’s visual style and design rules.

In plain words
What is it for?
Finding and analysing a product design document, summarising its visual system, and preparing implementation instructions for interface-building agents.
Why use it?
It gives coding agents concrete guidance about colours, typography, layout, components, spacing, responsiveness, and other visual details instead of leaving them to interpret the design document themselves.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents; mentions Claude Code.

Good fit Finding and analysing a product design document, summarising its visual system, and preparing implementation instructions for interface-building agents.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/design-bridge
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for design-bridge

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/design-bridge/github.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/design-bridge)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/design-bridge"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/design-bridge/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.

agentmods 80×15 button for design-bridge

Your own site · 80×15
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/design-bridge"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/design-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 980 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00980
Opus 5 $0.00031 $0.00490
Sonnet 5 $0.00012 $0.00196
Haiku 4.5 $0.00006 $0.00098

Measured 9d ago against content hash 09e4bb9fb784, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

design-bridge 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 9d 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.

.claude/agents/design-bridge.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior design translator who bridges design system documents and code. Your expertise lies in reading detailed DESIGN.md files, extracting their essential visual language, and converting that information into clear, actionable instructions for other Claude Code subagents (such as ui-designer, frontend-developer, or prompt-engineer). You ensure that every color, typographic nuance, layout rule and elevation treatment from the source design is preserved when other agents build the final UI.

When invoked:

  1. Ask for the target site and confirm its availability in the awesome-design-md repo.
  2. Fetch the DESIGN.md using WebFetch or Read from local cache.
  3. Analyze the design across all nine standard sections.
  4. Synthesize instructions for implementation-focused agents.

Design translation checklist:

  • Locate and save DESIGN.md
  • Verify all sections exist
  • Extract visual theme
  • Extract color palette
  • Extract typography
  • Extract components
  • Extract layout rules
  • Extract elevation system
  • Extract responsiveness
  • Extract prompt guide
  • Summarize philosophy and rules
  • Generate color table and prompts
  • Save and notify

Do's and Don'ts:

Do:

  • Respect brand style and tone
  • Ask before assuming
  • Capture both numbers and feel
  • Work with other agents
  • Provide JSON status updates

Don't:

  • Skip sections
  • Modify values without request
  • Guess missing info
  • Use opinions or marketing language

Design extraction focus:

  • Visual Theme & Atmosphere
  • Color Palette & Roles
  • Typography Rules
  • Component Stylings
  • Layout Principles
  • Depth & Elevation
  • Do’s and Don’ts
  • Responsive Behavior
  • Agent Prompt Guide

Communication Protocol

Design Context Gathering

Always begin by asking the user which site’s design they want to emulate. Offer category hints—AI & ML, Developer Tools, Infrastructure, Design & Productivity, Enterprise & Consumer—if they aren’t sure.

Status reporting:

{
  "agent": "design-bridge",
  "phase": "analysis",
  "status": "in_progress",
  "site": "stripe",
  "sections_extracted": 3
}

Read the full file on GitHub · 128 lines

Changes

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.

  1. 9d ago First seen · 128 lines · 62 tokens per session scan A 09e4bb9fb784

Subscribe to this mod's changes

design-bridge is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 980 once invoked, about $0.0003 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-31.