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 commands/laith0003/ux-skill/ux-systemgit clone --depth 1 https://github.com/Laith0003/ux-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/commands/laith0003/ux-skill/ux-system)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-system"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-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.00102 | $0.02568 |
| Opus 5 | $0.00051 | $0.01284 |
| Sonnet 5 | $0.00020 | $0.00514 |
| Haiku 4.5 | $0.00010 | $0.00257 |
Grade A, and why
ux-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 5d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-system
You are running the /ux-system command from the ux plugin. The job is to propose a complete starter design system for a project that lacks one. Tokens, foundations, component contracts, dark-mode pairings, theme switcher. Not a sketch — a usable starter.
When to use
Triggers: "we don't have a design system", "build us a system", "propose tokens", "what should our theme be", "set up our DS", "we need a token JSON", "design our brand foundations".
If the project already has a design system, do not run this. Recommend /ux-component against the existing system instead.
Process
0. Discovery protocol (MANDATORY)
Before anything else, read references/process/discovery-protocol.md and run its intake. For design systems, load-bearing fields: brand identity (existing tokens, logo, colors, type), reference inspirations (admired systems), audience (operator / consumer / mixed), style direction, voice, stack, must-have patterns (specific components or tokens), avoid-list, and the wow moment. Group into 2 messages. Skip only on --skip-discovery or full-spec input. Without the wow moment, push back.
1. Capture inputs
Required:
- Source material: a brand brief, an existing site to derive from, a screenshot of inspiration, OR explicit "your call" with the target product type
- Target stack: Tailwind / CSS variables / Styled Components / Stitches / vanilla CSS / Blade + Tailwind / etc.
- Output path: default
design-system/in the target project root; configurable
If anything's missing, ask once: "Source material (brief / site / 'your call'), target stack, and output path? Or say 'defaults' and I'll pick."
2. Read the references
Read before dispatching:
references/styles/anti-slop.md— bans the architect must respectreferences/styles/arsenal.md— patterns the components should supportreferences/system/foundations.mdif present — house style for foundations- Any existing
design-system/files in the target — do not overwrite, propose alongside
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.
- 5d ago First seen · 217 lines · 102 tokens per session scan A 2ef52ba78337
ux-system is a command published in the GitHub repository Laith0003/ux-skill (65 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 2,568 once invoked, about $0.0005 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-30.
Other commands, from other repositories
design-system
Generate design tokens, theme configuration, or extract a design system from existing code or Figma files.
figma-sync
Detect drift between Figma designs and code implementation — compare tokens, spacing, colors, typography, and component structure.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
spacing-layout-specialist
Use when spacing looks arbitrary. Padding and margins off any scale, inconsistent gaps between the same components, no grid underneath, or a layout that needs a denser mode.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.