design-system

design-system is a skill for Claude Code from coroboros/agent-skills. It costs 61 tokens per session (4,427 once invoked), scanned A, original, MIT.

A design-system skill that governs an existing DESIGN.md file during user-interface work. DESIGN.md records the approved visual rules for colors, type, spacing, and corner shapes, while the skill also supports auditing, comparison, export, migration, and setup tasks.

In plain words
What is it for?
Use it when editing UI components, pages, layouts, styles, or design tokens, or when checking, exporting, migrating, or initializing a DESIGN.md system.
Why use it?
It helps keep interface changes aligned with the project's documented visual rules and exposes drift between the rules and the code.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Part of the design-skills plugin — 3 skills shipped together

Good fit Use it when editing UI components, pages, layouts, styles, or design tokens, or when checking, exporting, migrating, or initializing a DESIGN.md system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/coroboros/agent-skills/design-system
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.

Any agent
npx skills add coroboros/agent-skills --skill design-system
Clone the repo
git clone --depth 1 https://github.com/coroboros/agent-skills

Made for: Claude Code.

Or install design-skills, the plugin that ships this one along with the rest of its 3 skills.

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-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/coroboros/agent-skills/design-system.svg)](https://agentmods.dev/skills/coroboros/agent-skills/design-system)
Your own site
<a href="https://agentmods.dev/skills/coroboros/agent-skills/design-system"><img src="https://agentmods.dev/badge/skills/coroboros/agent-skills/design-system.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,427 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.00061 $0.04427
Opus 5 $0.00030 $0.02214
Sonnet 5 $0.00012 $0.00885
Haiku 4.5 $0.00006 $0.00443

Measured today against content hash 81e750731fe5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

design-system 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.

The scan reads SKILL.md. This mod also ships 8 executable files (scripts/audit_extensions.py, scripts/audit-extensions.sh, scripts/audit.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/design-system/SKILL.md · 201 lines

How it starts

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

Design System

Two modes for governing a project's visual identity:

  1. Auto-activate — when editing UI files (components, pages, layouts, styles, DESIGN.md, tailwind.config.*) and a DESIGN.md is present, the skill reads it first and enforces token-only sourcing for colors, typography, spacing, and corner radius. No DESIGN.md? It stays out of the way — a one-line pointer to /award-design or /frontend-dev, no enforcement, no block on the edit.
  2. Subcommands/design-system <verb> [path] exposes the full DESIGN.md lifecycle, built on the canonical @google/design.md CLI.

Subcommand routing

Parse the first positional invocation argument. If it matches a verb below, load the referenced file and follow its workflow. Otherwise proceed with the token-enforcement workflow at the end of this document.

First token Mode Reference
audit (aliases: check, lint) Lint + fix proposals, human-readable report references/subcommand-audit.md
diff Regression check between versions (git-aware) references/subcommand-diff.md
export Tokens → Tailwind theme or W3C DTCG tokens.json references/subcommand-export.md
spec Emit the canonical spec from the installed CLI references/subcommand-spec.md
migrate Port legacy Stitch 9-section DESIGN.md → Google standard references/subcommand-migrate.md
init Scaffold a minimal valid DESIGN.md (fallback from /award-design) references/subcommand-init.md
audit-extensions Bidirectional drift check — DESIGN.md extension YAML ↔ prose refs ↔ globals.css @theme references/subcommand-audit-extensions.md
(none, or a UI file path) Token enforcement — see the default workflow at the end (this file)

Source of truth

When a DESIGN.md exists at the project root, read it before writing any UI code: every color, font, spacing value, corner radius, and component style comes from this file — the YAML frontmatter tokens (normative values) or the prose explaining when and why to apply them.

Read the full file on GitHub · 201 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. today Changed · -1 lines · -27 tokens per session 81e750731fe5
  2. 5d ago Changed b7897c1947ff
  3. 8d ago First seen · 202 lines · 88 tokens per session scan A 564e458debdf

Subscribe to this mod's changes

design-system is a skill published in the GitHub repository coroboros/agent-skills (4 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 4,427 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.