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 TaewoooPark/UIForge/plugin install uiforgeWrote 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/taewooopark/uiforge/design-tokens)<a href="https://agentmods.dev/skills/taewooopark/uiforge/design-tokens"><img src="https://agentmods.dev/badge/skills/taewooopark/uiforge/design-tokens/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/taewooopark/uiforge/design-tokens"><img src="https://agentmods.dev/badge/skills/taewooopark/uiforge/design-tokens.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.00147 | $0.01591 |
| Opus 5 | $0.00073 | $0.00796 |
| Sonnet 5 | $0.00029 | $0.00318 |
| Haiku 4.5 | $0.00015 | $0.00159 |
Grade A, and why
design-tokens 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 11d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Tokens — emit first, enforce always
Token-first, enforced at generation time, is the single mechanism most correlated with "designed vs slop" output across every premium AI-UI tool (v0 mandates tokens; Lovable scans each generation for violations and auto-corrects; Subframe cascades them). Do the same: emit the signature before the first component, then let nothing use a value that isn't in it.
1. Emit tokens.css before any component
Don't start from a blank page — that's how the median wins. Start from a
kit: copy the chosen direction's ready theme from
${CLAUDE_PLUGIN_ROOT}/tools/kits/ (each ships a real, non-default typeface, a
committed palette, radius/shadow, and a reduced-motion path — and already passes
the linter). Install its fonts (the header line: npm i @fontsource…). Or run
/uiforge:reskin <image|url> to derive tokens from a reference. The bare
${CLAUDE_PLUGIN_ROOT}/tools/tokens.template.css is the fallback when no kit
fits. Tune the roles to the brand, but keep components consuming var(--…) or
the generated utilities (bg-bg, text-fg, bg-primary, bg-surface,
text-muted, border-border) — never literals:
:root {
/* color — semantic ROLES, not raw hex at point of use */
--bg: …; --fg: …; /* base surface + text */
--surface: …; --on-surface: …; /* raised card + its text */
--muted: …; --border: …; /* secondary text, hairlines */
--primary: …; --on-primary: …; /* the ONE accent + its text */
--ring: …; /* focus ring, ≥3:1 */
/* space — 8px grid (4px half-step); ONE scale */
--space-1: 4px; --space-2: 8px; --space-3: 12px; --space-4: 16px;
--space-6: 24px; --space-8: 32px; --space-12: 48px; --space-16: 64px;
/* radius — one vocabulary */
--radius-sm: …; --radius: …; --radius-lg: …;
/* elevation — one light source, monotonic */
--shadow-1: 0 1px 2px rgb(0 0 0 / .06);
--shadow-2: 0 2px 6px rgb(0 0 0 / .08);
--shadow-3: 0 8px 24px rgb(0 0 0 / .12);
/* type — sizes from ONE ratio; role line-heights */
--text-xs: …; --text-sm: …; --text-base: 16px; --text-lg: …;
--text-xl: …; --text-2xl: …; --text-3xl: …; --text-display: …;
--leading-tight: 1.1; --leading-snug: 1.25; --leading-normal: 1.5;
--font-display: …; --font-text: …; --font-mono: …;
}
What ships with it
3 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.
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.
- 11d ago First seen · 114 lines · 147 tokens per session scan A 5704aef0960d
design-tokens is a skill published in the GitHub repository TaewoooPark/UIForge (7 stars, last pushed 1mo ago), licensed MIT. It adds 147 tokens to every session and 1,591 once invoked, about $0.0007 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
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
design-spatial
Spatial composition and layout for frontend design. Load with design when composing pages/dashboards/components, or whenever generated UI looks off — overlapping/colliding elements, weak hierarchy, or generic ("looks like every startup site"). The core idea: a model can't trust its own layout, so render it, critique…
design-tokens
This skill should be used when a user wants to scaffold or refactor a design token system — e.g. "set up design tokens", "create a design system foundation", "extract these hardcoded colors into tokens", "add a type scale", "theming setup", or "dark mode tokens". It produces a single source of truth for color, type…
design-system
Mechanical implementation invariants for frontend design: token architecture, typography hierarchy, loading order, FOUT prevention, chrome stability, motion timing, color semantics. Use with design when building components, pages, or design systems. (Aesthetic direction lives in design-thinking; anti-trend/anti-slop…
ckw-design
Entry point for frontend design. Use WHENEVER building or touching the look of any web UI — components, pages, dashboards, landing pages, React/Vue/HTML-CSS — and whenever the user says "make this look better/nicer", "fix the spacing/layout", or mentions styling, color, typography, fonts, responsive design, polish, or…
interaction-feedback
This skill should be used when the user wants clear visual feedback for async actions and state changes — triggers like "add loading and error states", "show a success message", "add a toast/notification", "inline form validation", "optimistic UI", "empty state for this list", "this button gives no feedback", or "add…