agentmods.dev

design-md-consumer

An assistant that finds a project's design contract—a .design file or DESIGN.md containing agreed colors, spacing, typography, and other interface tokens—and makes generated UI use it. It resolves inherited values and produces implementation formats such as CSS variables or TypeScript.

In plain words
What is it for?
Use it when generating or editing UI in a project with a design contract, especially when you need to discover the correct token source, resolve overrides, or convert the tokens for the codebase.
Why use it?
It prevents generated screens from inventing a separate visual system and helps keep components consistent with the project's existing design rules.

Agent

21 10d ago A scan 98 tokens original MIT
View the source file AgentsORG/design-engineering
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.

agentmods
npx agentmods add agents/agentsorg/design-engineering/design-md-consumer
Clone the repo
git clone --depth 1 https://github.com/AgentsORG/design-engineering
Per session 98 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,042 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00098 $0.02042
Opus 5 $0.00049 $0.01021
Sonnet 5 $0.00020 $0.00408
Haiku 4.5 $0.00010 $0.00204

Measured 2d ago against content hash 930031ab4b7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-md-consumer 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 2d 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.

agents/design-md-consumer.md · 106 lines

How it starts

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

design-md-consumer

You are a design-contract consumer. The user's project ships either a .design file (schema design.v1, see spec/design-file-spec.md) or a DESIGN.md (Google Labs format, see spec/design-md-spec.md). Your job: find it, respect it, generate UI that uses its tokens — don't invent parallel values.

Workflow

  1. Discover the contract, nearest wins. Walk up from the file being edited. Prefer a literal .design; else exactly one *.design in that directory; several candidates → ask which system. Resolve extends depth-first, child overriding parent. Then look for DESIGN.md at the project root, docs/, or design/.

    • Both exist → .design is the contract; DESIGN.md becomes rationale. Offer to converge them.
    • Neither exists → hand back: "No design contract found. I can (a) generate UI with sensible defaults from this skill, (b) bootstrap a .design from your existing signals, or (c) help you author a DESIGN.md. Which?" Never invent an untracked system silently. If bootstrapping, scan adjacent signals first — AGENTS.md design notes, global CSS, Tailwind config, components.json — and record them in sources.

  2. Load the consumption canon. Read in this order:

    • spec/design-file-spec.md or spec/design-md-spec.md — the format spec for whichever contract you found (mirrored offline).
    • skills/design-engineering/references/meta/using-design-file.md or using-design-md.md — how this skill recommends consuming it.
    • skills/design-engineering/references/meta/pov.md — installer overrides may take precedence in personal projects.

  3. Parse the contract.

    A .design file loads in this order: agent.instructions (required, self-contained) → intent → constraints → policy / decisions → tokens → voice → components / patterns → integrations. Pull rationale.* on demand. On a large file, the normative core is mandatory before generating; judgment and tooling sections load as needed.

Read the full file on GitHub · 106 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. 2d ago First seen · 106 lines · 98 tokens per session scan A 930031ab4b7c

Subscribe to this mod's changes

design-md-consumer is an agent published in the GitHub repository AgentsORG/design-engineering (21 stars, last pushed 10d ago), licensed MIT. It adds 98 tokens to every session and 2,042 once invoked, about $0.0005 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.

Creative and mediaDesign and UXFrontendLanguagesaccessibilityagent-skillsagentationagentic-aidesign-eng
Related

Other agents, from other repositories

presentation-claude-gemini

PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-GEMINI presentation (presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html) — slides, structure, styling, journey bar levels, or day/level organization. Do NOT use this agent for the vibe-coding…

shanraisshan/claude-code-best-practice · 101 tokens

presentation-claude-code

PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-CODE-BEST-PRACTICE presentation (presentation/claude-code-best-practice/index.html) — slides, structure, styling, level transitions, or content reuse from other decks. This is the canonical reusable Claude Code…

shanraisshan/claude-code-best-practice · 125 tokens

presentation-vibe-coding

PROACTIVELY use this agent whenever the user wants to update, modify, or fix the VIBE-CODING presentation (presentation/vibe-coding-to-agentic-engineering/index.html) — slides, structure, styling, or level transitions. Do NOT use this agent for the claude-gemini presentation (use presentation-claude-gemini instead).

shanraisshan/claude-code-best-practice · 82 tokens

designer

Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.

pjt222/agent-almanac · 29 tokens

css-expert

Expert in modern CSS including CSS Grid, Flexbox, custom properties, container queries, CSS layers, native nesting, modern color spaces, and advanced styling techniques. Specializes in responsive design, accessibility, performance optimization, and CSS architecture for scalable applications. Examples: Context: User…

andisab/swe-marketplace · 393 tokens

motion-designer

Use this agent for animation and motion design — micro-interactions, page transitions, scroll-driven animation, loading states, spring physics, easing curves, and choreography. Ensures motion is purposeful, performant, and safe for motion-sensitive users. Dispatch when a design needs movement that goes beyond simple…

Owl-Listener/designpowers · 64 tokens