design-token-guard

design-token-guard is a skill for Claude Code from ivy00johns/Skill-Madness. It costs 221 tokens per session (2,360 once invoked), scanned A, original, MIT.

A source-code check for frontend styling that keeps components using a project's shared design tokens instead of hardcoded colors or inline styles. Design tokens are named, reusable style values such as colors and spacing.

In plain words
What is it for?
It finds inline styles and hardcoded colors, identifies the token that should replace each one, and can add checks to ESLint, pre-commit hooks, and CI.
Why use it?
Visual tests can look correct even when code bypasses the design system, making later style changes harder and allowing inconsistent styling to spread.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Part of the skill-madness plugin — 80 skills shipped together

Good fit It finds inline styles and hardcoded colors, identifies the token that should replace each one, and can add checks to ESLint, pre-commit hooks, and CI.

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

Made for: Claude Code.

Or install skill-madness, the plugin that ships this one along with the rest of its 80 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-guard

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/design-token-guard"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/design-token-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 221 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,360 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.00221 $0.02360
Opus 5 $0.00111 $0.01180
Sonnet 5 $0.00044 $0.00472
Haiku 4.5 $0.00022 $0.00236

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

Security

Grade A, and why

design-token-guard 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 10d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (assets/eslint-tokens.snippet.mjs, scripts/check_design_tokens.py), 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/workflows/design-token-guard/SKILL.md · 172 lines

How it starts

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

design-token-guard

The problem this solves

A hardcoded color renders identically to the token it should have used. style={{ background: "#07090c" }} and style={{ background: "var(--tl-tooltip)" }} produce the same pixels. So every render-level gate — visual review, e2e, screenshots, "console is clean" — passes a component that has silently bypassed the design system. The violation only exists in source.

That is why inline styles and hardcoded CSS accumulate invisibly until someone eyeballs the code weeks later and burns hours on a token refactor. The fix is a source-level gate: a deterministic check that reads the diff for styling that bypasses the token system, run before the code is declared done, and wired into the repo so it can't regress.

This skill is that gate. It does two things:

  1. Audit — run the bundled checker (scripts/check_design_tokens.py) to find every inline style and hardcoded color, each mapped to the exact token to use.
  2. Enforce — scaffold the check into the repo (config + ESLint rule + pre-commit hook + lint:tokens script) so the gate runs on every commit/CI, not just when an agent remembers to look.

It is dynamic: it auto-discovers whatever token system the project already uses and derives the rules from it. TruthLens and a vanilla Vue app are two configs of one skill, not two skills.

Step 1 — Audit

Run the checker from the project root. It needs no flags for a first pass:

python3 <skill-dir>/scripts/check_design_tokens.py --root .

What it does automatically:

  • Discovers the token source — scans for CSS custom properties (--name: …), SCSS/Less vars ($name, @name), JS/TS theme objects, or design-token JSON. From those it builds a color-value → token map.
  • Scans the source tree (.tsx/.ts/.jsx/.js/.vue/.svelte/.astro/.html), skipping node_modules, build dirs, config files, and the token files themselves.
  • Reports each finding as file:line:col, the offending snippet, and — when the literal matches a declared token — the exact fix:

Read the full file on GitHub · 172 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 172 lines · 221 tokens per session scan A 146d18894966

Subscribe to this mod's changes

design-token-guard is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 2d ago), licensed MIT. It adds 221 tokens to every session and 2,360 once invoked, about $0.0011 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.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

frontend-ui-dark-ts

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.

microsoft/skills · 48 tokens

reveal-hover-effect

Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…

MengTo/Skills · 66 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens