Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ZachArticulateV/designer-pro-and-seo/plugin install designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/design-tokens-emit)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/design-tokens-emit"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-tokens-emit/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/zacharticulatev/designer-pro-and-seo/design-tokens-emit"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-tokens-emit.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.00076 | $0.00636 |
| Opus 5 | $0.00038 | $0.00318 |
| Sonnet 5 | $0.00015 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
design-tokens-emit 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 12d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-tokens-emit
Family: design Status: Stable
Purpose
Bridge "we have a design system spec" to "we have tokens we can import." Takes a
design-system-gen result and emits real token files in the chosen format(s), so
the palette/typography/effects become part of the build instead of staying a doc.
Triggers
- "emit tokens" / "convert design system to code"
- "tailwind config" / "css variables" / "style dictionary"
- "tokens for [tailwind/css/scss]"
Inputs
- A design system as engine JSON from
design-system-gen(re-run it in JSON mode if you only have a savedMASTER.md— the emitter reads JSON, not Markdown) - Target format:
css|tailwind|scss|json|all - Output directory
Steps
- Get the design JSON. Run
design-system-gen(JSON mode) or read a saved one. - Emit tokens:
On Windows, usepython3 "${CLAUDE_PLUGIN_ROOT}/scripts/design/tokens_emit.py" --design-json ds.json --format all --out-dir tokens/pyifpython3is absent; in PowerShell the variable is$env:CLAUDE_PLUGIN_ROOT. Producestokens.css(:rootcustom properties),tailwind.tokens.js(merge intotheme.extend),_tokens.scss, andtokens.json(Style-Dictionary shape). Use--printto preview without writing. - Wire it in. Tell the user where each file goes (import the CSS, merge the
Tailwind fragment,
@usethe SCSS) and include the contrast-safeon_primarycolor for button text. - Keep it in sync. Re-run when the design system changes; tokens are generated, not hand-maintained.
Outputs
- One token file per requested format (CSS / Tailwind / SCSS / JSON)
- Wiring notes for the target stack
Dependencies
scripts/design/tokens_emit.py(required) — Python 3.10+, standard library onlydesign-system-gen(required) — upstream source of the design JSON the emitter reads
Notes
Pairs with design-build (which consumes the tokens) and design-system-persist
(which stores the source design system). SwiftUI/Compose targets are on the roadmap;
web formats ship today.
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.
- 12d ago First seen · 63 lines · 76 tokens per session scan A d13b6bec3557
design-tokens-emit is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 636 once invoked, about $0.0004 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.
Other skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
web-design
A web design workflow for turning a brief, reference website, screenshot, or keywords into a design specification and then web code. It covers visual style, page structure, interaction, responsive layouts, and motion.
design-to-code-check
Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
Component Variants / States Documentation コンポーネント状態の文書化
A code review check for new reusable interface components and the variations and states they support, such as hover, focus, disabled, loading, and error states.
Design Source-of-Truth Conformance デザイン定義準拠
A code review check that compares new interface values—such as colors, spacing, font sizes, rounded corners, and shadows—with the project's documented design rules or token files. It only runs when those design definitions exist.