What is design-tokens?

A command for organizing the reusable values behind a visual design system, such as colors, spacing, fonts, borders, and component settings. It supports primitive, semantic, and component layers, plus light and dark themes.

Use it to define tokens for colors, spacing, typography, buttons, inputs, cards, and themes.

It helps keep an interface visually consistent and makes broad design changes easier to manage. It also accounts for accessibility contrast requirements.

design-tokens — Command for Claude Code by sairam0424

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/sairam0424/MindForge

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sairam0424/mindforge/design-tokens/github.svg)](https://agentmods.dev/commands/sairam0424/mindforge/design-tokens)

Your own site

<a href="https://agentmods.dev/commands/sairam0424/mindforge/design-tokens"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/design-tokens/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sairam0424/mindforge/design-tokens"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/design-tokens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,182 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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.01182
Opus 5	$0.00015	$0.00591
Sonnet 5	$0.00006	$0.00236
Haiku 4.5	$0.00003	$0.00118

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

Security

Grade A, and why

design-tokens 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 5d 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/commands/mindforge/design-tokens.md · 81 lines

How it starts

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

<execution_context> @.mindforge/skills/design-system/SKILL.md </execution_context>

Map to semantic tokens: Create meaningful aliases:
- color-primary → blue-600, color-primary-hover → blue-700
- color-surface → white, color-surface-elevated → gray-50
- color-text-primary → gray-900, color-text-secondary → gray-600
- color-border → gray-200, color-border-focus → blue-500
- color-success → green-600, color-warning → amber-600, color-error → red-600
- spacing-page → 6x, spacing-section → 4x, spacing-element → 2x
- font-heading → sans/bold, font-body → sans/regular, font-code → mono/regular
- Ensure all semantic tokens pass WCAG 2.1 AA contrast ratios (4.5:1 for text, 3:1 for UI)
Derive component tokens: Map semantic tokens to component-specific usage:
- button-bg → color-primary, button-text → color-on-primary
- button-radius → radius-md, button-padding → spacing-2x spacing-4x
- input-border → color-border, input-border-focus → color-border-focus
- input-bg → color-surface, input-text → color-text-primary
- card-bg → color-surface-elevated, card-shadow → shadow-md
- card-radius → radius-lg, card-padding → spacing-4x
- Each component token references semantic tokens (never primitives directly)
Implement theming: Support dark and light modes:
- Dark theme overrides semantic layer only (primitives stay constant)
- color-surface → gray-900 (dark), color-text-primary → gray-100 (dark)
- color-border → gray-700 (dark), color-surface-elevated → gray-800 (dark)
- Shadows: reduce opacity in dark mode, add subtle inner glow
- Ensure all dark theme combinations meet contrast requirements
- Implementation: CSS custom properties with [data-theme="dark"] selector
- System preference detection: prefers-color-scheme media query as default
Document in Storybook: Create documentation artifacts:
- Token reference page: all tokens with visual swatches and values
- Usage guidelines: when to use which semantic token
- Do/Don't examples: correct vs incorrect token usage
- Accessibility notes: contrast ratios, focus indicators, motion preferences
- Migration guide: how to adopt tokens in existing components
- Playground: interactive token picker for designers
Version the token system: Establish governance:
- Semantic versioning for the token package (major.minor.patch)
- Breaking change: removing a token or changing its type → major bump
- Addition: new token → minor bump
- Value change: updating a token value → patch bump
- Deprecation process: mark deprecated, provide migration path, remove in next major
- Change log: document every token change with rationale
- Distribution: npm package, Figma plugin sync, design tool integration

Read the full file on GitHub · 81 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.

5d ago First seen · 81 lines · 31 tokens per session scan A 5bd802c5d57b

Subscribe to this mod's changes

design-tokens is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 1,182 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-09-03.

CSS and styling Design and UX Frontend agent-orchestration agent-skills agentic-workflows ai-agents anthropic antigravity

design-tokens

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

What this file has done since we first saw it

Other commands, from other repositories

p3-ux-darkmode

ui-review

shadcn-ui

style-guide

prototype

ccc-multi-frontend