apply-design-md

A command that reads a project's design contract, stored in a .design file or DESIGN.md, and applies its stated colors, spacing, typography, and component rules to interface code. It can map those rules to CSS, Tailwind, or design-system components.

In plain words
What is it for?
It helps update a specified UI according to an existing design contract, including translating design tokens into CSS variables or other code-level values.
Why use it?
Design decisions often become scattered across code or are replaced by outdated hard-coded values. This keeps the requested interface aligned with the project's documented design rules.

Command

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 commands/agentsorg/design-engineering/apply-design-md
Clone the repo
git clone --depth 1 https://github.com/AgentsORG/design-engineering
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 346 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.00036 $0.00346
Opus 5 $0.00018 $0.00173
Sonnet 5 $0.00007 $0.00069
Haiku 4.5 $0.00004 $0.00035

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

Security

Grade A, and why

apply-design-md 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.

commands/apply-design-md.md · 19 lines

What it actually says

Apply the design contract

Spawn or emulate the design-md-consumer subagent (agents/design-md-consumer.md).

  1. Discover the contract, nearest wins: walk up for a .design / *.design, resolving extends. Then check for DESIGN.md at the root, docs/, or design/. If both exist, .design is the contract and DESIGN.md is rationale.
  2. Load skills/design-engineering/references/meta/using-design-file.md (or using-design-md.md) plus pov.md.
  3. For a .design, read the normative core before generating: agent.instructionsintentconstraintspolicy / decisionstokensvoicecomponents.
  4. Output token mappings and apply them to the target UI the user specified. If integrations.shadcn.enabled, write css_vars into the declared CSS file — tokens outrank stale literals.
  5. Tokens and structured rules are normative; rationale and DESIGN.md prose are context.

Precedence when they disagree: user prompt → the contract → this skill → model defaults.

If no contract exists, say so and offer to bootstrap one — copy templates/design-engineering.design (this skill's canonical motion and surface defaults) or scaffold a DESIGN.md from spec/design-md-spec.md. Scan adjacent signals first; never invent an untracked system silently.

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 · 19 lines · 36 tokens per session scan A 671ed5895a37

Subscribe to this mod's changes

apply-design-md is a command published in the GitHub repository AgentsORG/design-engineering (21 stars, last pushed 10d ago), licensed MIT. It adds 36 tokens to every session and 346 once invoked, about $0.0002 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.