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 agentmods add skills/yogasw/wick/design-systemnpx skills add yogasw/wick --skill design-systemgit clone --depth 1 https://github.com/yogasw/wickWrote 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/yogasw/wick/design-system)<a href="https://agentmods.dev/skills/yogasw/wick/design-system"><img src="https://agentmods.dev/badge/skills/yogasw/wick/design-system.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.01921 |
| Opus 5 | $0.00033 | $0.00960 |
| Sonnet 5 | $0.00013 | $0.00384 |
| Haiku 4.5 | $0.00007 | $0.00192 |
Grade A, and why
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 4d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System
Enforces the project's visual language whenever Claude writes or edits UI
code — templ components, Tailwind classes, CSS tokens, theme files, or
tailwind.config.*. Every rule below is derived from the living token set
in tailwind.config.js and web/src/input.css.
When this skill activates
- Creating, editing, or refactoring a UI component (button, input, card, modal, dialog, tab, list, badge, notification, nav, layout, etc.)
- Writing or updating CSS, Tailwind classes, design tokens, theme
variables, or
tailwind.config.* - Choosing colors, font sizes, spacing, padding, margins, border-radius, shadows, or icon sizes
- Building a page layout, grid, container, or responsive breakpoint
Skip for purely backend / non-visual work.
Core rules
-
Inter font only. All text uses
Interviafont-sans. No other typeface in the UI. -
8-pixel grid. Spacing, padding, margin, width, and height are multiples of 8 (
8, 16, 24, 32, 40, 48, 56, 64, 72, 80). The sub-8 exceptions4px,12px, and20pxare allowed when 8-grid is too coarse. -
Named tokens only. Every color maps to a Tailwind token defined in
tailwind.config.js(seetokens.md). Raw hex is allowed only inside the token definition itself. -
Accent vs. status separation.
green-*is the primary accent color — never reuse it for "success."navy-*is for dark surfaces and login — never reuse it for "info." Status intent uses the dedicated ramps:pos-*,prog-*,cau-*,neg-*,error-*,warning-*,link-*. -
Text from Black ramp. All body/title/paragraph text uses
black-600throughblack-900. Never color body text with green or navy. -
Dark + light mode required. Every color class must have a
dark:counterpart. Use the themed CSS-variable tokens (navy-*,black-*,white-*) so themes work automatically. See the "Theming" section below. -
Mobile-first and responsive. Build for narrow viewports first, then layer
sm:/md:/lg:overrides. Test mentally at ≤375px before declaring done.
What ships with it
2 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.
- 4d ago First seen · 155 lines · 66 tokens per session scan A bc0ee9721d77
design-system is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,921 once invoked, about $0.0003 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
omh-accessibility-audit
This is a Hermes-native accessibility-audit workflow skill.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
n8n:content-design
Product content designer for UI copy. Use when writing, reviewing, or auditing user-facing text: button labels, error messages, tooltips, empty states, modal copy, placeholder text, confirmation dialogs, onboarding flows, or i18n strings. Also use when the user says /copy, /content, or /ux-copy.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
design-system-adoption
Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use design-system-governance (design-systems).
ux-writing
Write interface copy — microcopy, error messages, empty states, and CTAs. Use when the words are the deliverable. For content structure and ownership, use content-strategy (ux-strategy).