Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PMDevSolutions/Aureliusnpx agentmods add skills/pmdevsolutions/aurelius/design-token-lockWrote 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.
[](https://agentmods.dev/skills/pmdevsolutions/aurelius/design-token-lock)<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/design-token-lock"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/design-token-lock/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.
<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/design-token-lock"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/design-token-lock.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.03020 |
| Opus 5.5 | $0.00000 | $0.01208 |
| Sonnet 5.5 | $0.00000 | $0.00604 |
| Haiku 4.5 | $0.00000 | $0.00302 |
Grade A, and why
design-token-lock 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.
How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Token Lock — Single Source of Truth
Purpose
Solve the #1 recurring pain point in Figma-to-code: style drift. This skill extracts every design value from Figma, writes a versioned lockfile (design-tokens.lock.json), and generates Tailwind config + CSS custom properties from it. The lockfile becomes the single source of truth — tests assert against it, components reference it, and the verify-tokens script enforces it.
When to Use
- Phase 2 of the
/build-from-figmapipeline (afterfigma-intake) - Any time you need to extract or refresh design tokens from Figma
- When regenerating Tailwind config from a Figma file
Inputs
- Required: Figma file key (from build-spec.json or URL)
- Optional:
.claude/plans/build-spec.json(for component-specific token scoping)
Process
Step 1: Extract Tokens from Figma
Call Figma MCP to get all design values:
1. get_variable_defs(fileKey)
→ Color variables, typography variables, spacing variables
→ Variable collections and modes (light/dark)
2. get_design_context(fileKey, nodeId) — for each top-level frame
→ Computed styles on actual elements
→ Auto-layout padding, gap, corner radius values
→ Text styles with exact font-family, size, weight, lineHeight
3. get_screenshot(fileKey, nodeId) — for color reference verification
→ Visual reference to cross-check extracted values
Step 2: Build Token Structure
Organize extracted values into a normalized structure. Every value must trace back to Figma.
Color tokens:
- Extract from Figma variables first (most accurate)
- Fall back to computed styles on elements if no variables defined
- Record: hex, rgb, hsl, and suggested Tailwind class name
- Group: primitives (raw values), semantic (roles), component-specific
Typography tokens:
- Font family with full fallback stack
- Size scale in px and rem (assuming 16px base)
- Weight values (numeric, not named)
- Line height as unitless ratio
- Letter spacing in em
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.
- 1mo ago First seen · 280 lines · 0 tokens per session scan A 9a01cd74cbb9
design-token-lock is a skill published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,020 tokens. 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-04.
Other skills, from other repositories
mk:figma
Read-first Figma gateway via Figma MCP: analyze designs, implement Figma-to-code for 1–3 screens, extract design tokens, produce a Figma Evidence Packet for planning handoff, screenshot fallback. Advanced operations (Code Connect, canvas writes, design-system/library patterns) are gated references loaded only on…
generate-project-design-system
A draft generator that studies a project's code and Figma design data to prepare a design-system skill. A design system is a shared set of colors, sizes, components, and usage rules for keeping interfaces consistent.
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
refero-design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this…
producao-no-figma
Orientação para organização e produção em Figma: componentes, auto-layout e sistemas de design.