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 mae616/design-skills --skill ui-designergit clone --depth 1 https://github.com/mae616/design-skillsWrote 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/mae616/design-skills/ui-designer)<a href="https://agentmods.dev/skills/mae616/design-skills/ui-designer"><img src="https://agentmods.dev/badge/skills/mae616/design-skills/ui-designer/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/mae616/design-skills/ui-designer"><img src="https://agentmods.dev/badge/skills/mae616/design-skills/ui-designer.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.00038 | $0.00528 |
| Opus 5.5 | $0.00015 | $0.00211 |
| Sonnet 5.5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
ui-designer 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 2mo 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.
What it actually says
UI Designer Skill
When to Apply
Apply this skill when the request involves:
- UI/screen design, component design, information architecture, design system, visual hierarchy, layout structure, tone and manner
- 画面設計、UI方針、コンポーネント設計、情報設計、トーン&マナー、デザインシステム、画面の骨格
- Working with design files or design-related commands
Core Principles
- UI is not art, it's decision support. Help users achieve their goals as quickly as possible.
- Systematize repetition. Componentize repeated UI patterns; use tokens to prevent inconsistency.
- Specs include states. A complete spec covers loading, error, empty, and disabled states.
Design Philosophy (Decision Rules)
- Prioritize first. Decide what users see first vs. what can wait.
- Don't cram everything. Use progressive disclosure to reveal information in stages.
- Always define states. Normal / loading / empty / error / no-permission must be specified.
- Enforce consistency through rules. Components, tokens, spacing, and typography create coherence.
- Leave no ambiguity for implementers. Specs should be precise, not vague prose.
Initial Questions to Clarify
- What is the screen's goal? (What counts as success?)
- Who is the primary user? (Persona / usage context)
- What is the primary action?
- What are the edge cases? (Empty / error / permission / slow network)
- What is the reuse scope? (Page-specific or cross-cutting?)
Output Format (Follow This Order)
- Screen purpose / success criteria
- Information architecture (priority, structure)
- Component proposal (responsibility, props, states)
- Token / style guidelines (colors, spacing, typography)
- Edge state specs (empty / error / loading)
- Next actions (prototype → implementation)
Common Pitfalls
- Edge states left undefined, leading to ad-hoc implementation
- Visual inconsistencies not captured in tokens, causing magic numbers to proliferate
- Unclear screen purpose, causing element bloat
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.
- 2mo ago First seen · 54 lines · 38 tokens per session scan A ece42d9a62f9
ui-designer is a skill published in the GitHub repository mae616/design-skills (11 stars, last pushed 9mo ago), licensed MIT. It adds 38 tokens to every session and 528 once invoked, about $0.0002 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-31.
ui-designer compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ui-designermae616/design-skills | Skill | 11 | 9mo ago | MIT | A | 38 | Claude Code |
| webgl-holographic-foilnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 41 | Claude Code, Codex |
| html-ppt-hermes-cyber-terminalnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 53 | Claude Code, Codex |
| html-ppt-taste-brutalistnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 78 | Claude Code, Codex |
| visual-ralphYeachan-Heo/oh-my-codex | Skill | 34k | 4d ago | MIT | A | 52 | Codex |
| glance-canonical-layoutsandroid/skills | Skill | 10k | yesterday | Apache-2.0 | A | 56 | Claude Code |
| accessibilitymicrosoft/hve-core | Skill | 1.6k | yesterday | MIT | A | 47 | Claude Code |