design-token-audit

design-token-audit is a skill for Claude Code from skillmds/skillmd. It costs 17 tokens per session (380 once invoked), scanned A, a copy of design-token-audit, MIT.

An audit of how consistently a product uses design tokens, which are named values for visual properties such as colors, spacing, and typography. It checks token coverage, duplicate or deprecated tokens, hard-coded values, and missing tokens.

In plain words
What is it for?
Use it to inventory visual values in code and design files, match them to existing tokens, flag inconsistencies, and recommend new tokens or migrations.
Why use it?
It reveals where the product uses inconsistent values or bypasses its shared design rules. This gives the team a list of gaps and cleanup priorities.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the design-system-audit-and-remediation plugin — 14 skills shipped together

Good fit Use it to inventory visual values in code and design files, match them to existing tokens, flag inconsistencies, and recommend new tokens or migrations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/skillmds/skillmd/design-token-audit
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 skillmds/skillmd --skill design-token-audit
Clone the repo
git clone --depth 1 https://github.com/skillmds/skillmd

Made for: Claude Code.

Or install design-system-audit-and-remediation, the plugin that ships this one along with the rest of its 14 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-token-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/skillmds/skillmd/design-token-audit/github.svg)](https://agentmods.dev/skills/skillmds/skillmd/design-token-audit)
Your own site
<a href="https://agentmods.dev/skills/skillmds/skillmd/design-token-audit"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/design-token-audit/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.

agentmods 80×15 button for design-token-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/skillmds/skillmd/design-token-audit"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/design-token-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 380 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 100% copy Near-identical to another mod 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.00017 $0.00380
Opus 5.5 $0.00007 $0.00152
Sonnet 5.5 $0.00003 $0.00076
Haiku 4.5 $0.00002 $0.00038

Measured 1mo ago against content hash 78e0069a0a35, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-token-audit 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 1mo 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.

Origin

This is a copy

100% identical to design-token-audit — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/design-system-audit-and-remediation/skills/design-token-audit/SKILL.md · 40 lines

What it actually says

Design Token Audit

You are an expert in auditing design token adoption and consistency across products.

What You Do

You audit how design tokens are used (or not used) in a product, identifying inconsistencies, gaps, and hard-coded values.

Audit Scope

Token Coverage

  • What percentage of visual properties use tokens?
  • Which properties are commonly hard-coded?
  • Are the right tier of tokens used (global vs semantic vs component)?

Token Consistency

  • Are the same tokens used for the same purposes?
  • Are there redundant tokens (different names, same value)?
  • Are deprecated tokens still in use?

Token Gaps

  • Are there visual values that should be tokens but are not?
  • Are there use cases not covered by the existing token set?
  • Do custom values suggest missing token scale steps?

Audit Process

  1. Inventory — Extract all visual values from code/design files
  2. Categorize — Group by type (color, spacing, typography, etc.)
  3. Map — Match values to existing tokens
  4. Flag — Identify hard-coded values, mismatches, and gaps
  5. Prioritize — Rank issues by frequency and impact
  6. Recommend — Suggest new tokens, migrations, and cleanup

Audit Report Format

  • Executive summary (token adoption percentage, key findings)
  • Detailed findings by category
  • Hard-coded value inventory with suggested token replacements
  • Recommended new tokens
  • Migration plan and priority

Best Practices

  • Audit both design files and code
  • Automate detection where possible (lint rules)
  • Focus on high-impact categories first (color, spacing)
  • Track adoption over time
  • Make the audit results actionable, not just informational
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. 1mo ago First seen · 40 lines · 17 tokens per session scan A 78e0069a0a35

Subscribe to this mod's changes

design-token-audit is a skill published in the GitHub repository skillmds/skillmd (143 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 380 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to design-token-audit, differing in 1 line, and is treated as a copy.

Related

design-token-audit compared with skills from other repositories

design-token-audit next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-token-auditskillmds/skillmdSkill1434d agoMITA17Claude Code
frontendcode-yeongyu/lazycodexSkill3.9kyesterdayMITA79Codex
designlang-tokensManavarya09/design-extractSkill4.8k2d agoMITA30Claude Code
cli-anything-photoshopyb2460/harness-anythingSkill3.0k29d agoMITA43Claude Code, Codex
app-screenshot-debugtermio-sh/termioSkill7855d agoMITA161Claude Code, Codex
user-research-cookiycookiy-ai/user-research-skillSkill1.6k5d agoMITA154Claude Code, Codex
write-zot-themespatriceckhart/zotSkill360yesterdayMITA23Claude Code, Codex