design-system-author

design-system-author is a skill for Claude Code, Codex from evolplus/talos. It costs 69 tokens per session (9,586 once invoked), scanned A, original, Apache-2.0.

A guide for creating a shared Figma foundation of design tokens and reusable components before drawing screens. Design tokens are agreed values such as spacing, text sizes, colors, and button shapes.

In plain words
What is it for?
Use it when creating, revising, or importing Figma designs to define or reuse common styles and components, identify missing design rules, and check token compliance.
Why use it?
It prevents each screen from inventing its own visual rules, which causes inconsistent spacing, typography, buttons, and alignment. It also checks that screens follow the shared foundation before handoff.

Skill for Claude CodeCodex

Part of the talos plugin — 62 skills, 2 commands, 4 hooks shipped together

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 skills/evolplus/talos/design-system-author
Any agent
npx skills add evolplus/talos --skill design-system-author
Clone the repo
git clone --depth 1 https://github.com/evolplus/talos

Made for: Claude Code, Codex.

Or install talos, the plugin that ships this one along with the rest of its 62 skills, 2 commands, 4 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/evolplus/talos/design-system-author.svg)](https://agentmods.dev/skills/evolplus/talos/design-system-author)
Your own site
<a href="https://agentmods.dev/skills/evolplus/talos/design-system-author"><img src="https://agentmods.dev/badge/skills/evolplus/talos/design-system-author.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,586 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.00069 $0.09586
Opus 5 $0.00034 $0.04793
Sonnet 5 $0.00014 $0.01917
Haiku 4.5 $0.00007 $0.00959

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

Security

Grade A, and why

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

skills/design-system-author/SKILL.md · 506 lines

How it starts

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

Design System Author

When to use

You are the UI/UX Designer authoring or revising Figma content via MCP. Without a shared Foundation, every screen invents its own spacing scale (16px here, 12px there), text sizes (18pt vs 20pt for the same role), button radii (8px vs 12px), and alignment grid — drift compounds across screens and the Approver sees visual chaos at confirmation time. This skill is the content-hygiene complement to figma-canvas-layout (canvas-hygiene): same pre-handoff lint pattern, different concern.

Consult this skill:

  • In every Figma-writing mode (create / revise / incorporate) — apply the Foundation tokens, never invent ad-hoc values.
  • In import mode — extract what tokens already exist in the file; flag gaps as figma-design-system-gap open-issues.
  • As a pre-handoff lint — every mode, every dispatch.

Inputs and outputs

  • Inputs: SRS §3.4.1 Design References (UI surfaces), SRS ## Design System or brand-guidance section if present, the Figma file you're writing to via MCP.
  • Outputs: A Foundation Figma page (separate Figma page tab) containing tokens + components; every other page's frames consume from Foundation; an updated docs/uiux/handoffs/<task-id>.md enumerating tokens used; a pre-handoff token-compliance lint report appended to the handoff doc.

The Foundation page

Every Figma file the kit produces has a dedicated Foundation Figma page (separate page tab, NOT a section on a screens page). The Foundation page is the single source of truth for tokens + components. Screen pages reference it; screens never define their own colors, type styles, or spacing values.

Foundation is structured as five Figma sections. Before authoring those sections from scratch, run the Foundation-source selection step below — most projects inherit from a named preset, while Flow A projects may derive the Foundation from extracted Figma evidence.

Step 0 — Foundation source selection (run BEFORE any of Sections 1-5)

Read the full file on GitHub · 506 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. 4d ago First seen · 506 lines · 69 tokens per session scan A 7a1221203577

Subscribe to this mod's changes

design-system-author is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 9,586 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.