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/nicohodt/claude-code-ui-ux-skill/design-plangit clone --depth 1 https://github.com/nicohodt/claude-code-ui-ux-skillWhat 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.00017 | $0.00327 |
| Opus 5 | $0.00009 | $0.00163 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
design-plan 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 yesterday.
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.
This is a copy
100% identical to design-plan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Before writing any markup, produce a design system for: $ARGUMENTS
-
Run the
ui-ux-pro-maxdesign-system generator to get style + color tokens + typography + UX anti-patterns:python3 <ui-ux-pro-max-skill-path>/scripts/search.py "$ARGUMENTS" --design-system -p "Project"(Resolve
<ui-ux-pro-max-skill-path>from the installed skill — see CLAUDE.md.) -
Pull anything the brief needs specifically, e.g.:
--domain color "<industry> <mood>"for the palette / semantic tokens--domain typography "<mood>"for font pairing + imports--domain web-vitals "<page type>"for the performance budget--domain ux "<pattern>"for do/don't guidance
-
Then apply the frontend-design lens: state purpose / tone / constraints / differentiation, pick ONE tone, choose a single signature element, and reject any choice that reads like a generic AI default.
Output a compact token block (4–6 named colors, 2–3 type roles, spacing scale, one signature element) and a one-paragraph rationale. Do not start building until the tokens are decided.
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.
- yesterday First seen · 27 lines · 17 tokens per session scan A bd7298174dd6
design-plan is a command published in the GitHub repository nicohodt/claude-code-ui-ux-skill (2 stars, last pushed 29d ago), licensed MIT. It adds 17 tokens to every session and 327 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to design-plan, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
setup
Fetch Kobiton credentials from the authenticated MCP server and write them to /.kobiton/.credentials.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.