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.
npx skills add YuqingNicole/variant-design-skill --skill variant-design-systemgit clone --depth 1 https://github.com/YuqingNicole/variant-design-skillWrote 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/yuqingnicole/variant-design-skill/variant-design-system)<a href="https://agentmods.dev/skills/yuqingnicole/variant-design-skill/variant-design-system"><img src="https://agentmods.dev/badge/skills/yuqingnicole/variant-design-skill/variant-design-system/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/yuqingnicole/variant-design-skill/variant-design-system"><img src="https://agentmods.dev/badge/skills/yuqingnicole/variant-design-skill/variant-design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.04245 |
| Opus 5.5 | $0.00030 | $0.01698 |
| Sonnet 5.5 | $0.00015 | $0.00849 |
| Haiku 4.5 | $0.00007 | $0.00424 |
Grade A, and why
variant-design-system 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 21d 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before generating code, load
skills/shared/code-output.md,references/project-context.md, andreferences/quality-baseline.md.
For product-critical work, also read references/design-declaration.md and references/product-integrity-gate.md. A confirmed design system locks the declaration's product constraints as well as visual tokens.
Design System Mode
The canonical workflow for production-quality work. Define once, generate consistently.
ds → confirm → component [name] → compose [page]
↑ ↑ ↑
Token foundation Atomic pieces Assembled layouts
Triggers
| User says | Action |
|---|---|
ds / "create a design system" / "define tokens" / "set up tokens" |
Generate design system → preview → confirm |
ds confirm |
Lock the current design system and any product-critical Design Declaration for future outputs |
ds edit [section] |
Edit one section of the design system (palette / type / spacing / motion) without regenerating all |
ds show |
Print current design system token summary in terminal |
component [name] (after DS confirmed) |
Generate component using locked DS tokens, all 8 states |
compose [page name] |
Assemble confirmed components into a page, 3 layout variations |
compose [page] using A B C |
Compose page from specific named components |
Step 1 — Generate Design System (ds)
Before generating, infer these dimensions from the brief and repository. Ask at most two material unanswered questions across the entire request; no mandatory intake:
- Brand personality — 2–3 adjectives that describe the feel (e.g. "precise, warm, understated")
- Color direction — existing brand color, or a reference (hex / site URL / mood word)
- Typeface preference — existing fonts, or a direction ("editorial serif", "clean geometric sans", "monospace-forward")
If user says "surprise me" or has no preferences, infer from their codebase (README, existing CSS, component names) or pick a strongly opinionated direction and state it.
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.
- 21d ago Changed · +74 tokens per session c588fd62a72b
- 29d ago Changed · +4 lines e664d4c98fde
- 1mo ago First seen · 385 lines · 0 tokens per session scan A 98863a2d3f4e
variant-design-system is a skill published in the GitHub repository YuqingNicole/variant-design-skill (47 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 4,245 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
openclaw-carapace
Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
setting-up-charcoal-tailwind
Use before writing or editing code that uses @charcoal-ui with Tailwind, and whenever such a project's charcoal setup is unverified or incomplete. The v2 token route still needs the theme CSS and the .ch-token-v2 opt-in, which the preset does not supply.
choosing-charcoal-styling
Use before writing or editing any code that imports @charcoal-ui, and whenever a project's charcoal setup is unverified or incomplete. Decides between the CSS variables, Tailwind and styled-components routes, and names the setup steps that are silently missing in most projects.
setting-up-charcoal-styled
Use before writing or editing code that uses @charcoal-ui with styled-components, TokenInjector, createTheme or addThemeUtils, and whenever such a project's charcoal setup is unverified or incomplete.
choosing-charcoal-tokens
Use before choosing any color, text style, spacing, radius or border value in code that uses @charcoal-ui, and whenever a literal is about to be written where a token exists — a hex color, a px padding or gap, a font-size, a border-radius or border-width. Charcoal has one correct token for each of these and the choice…
frontend-design
A front-end coding tool for building distinctive web pages and interface components. It focuses on unusual layouts, visual styling, animations, and production-ready code rather than generic-looking screens.