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/qinghaoliqaq/autocoder/ui_design_systemnpx skills add qinghaoliqaq/AutoCoder --skill ui_design_systemgit clone --depth 1 https://github.com/qinghaoliqaq/AutoCoderWrote 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/qinghaoliqaq/autocoder/ui_design_system)<a href="https://agentmods.dev/skills/qinghaoliqaq/autocoder/ui_design_system"><img src="https://agentmods.dev/badge/skills/qinghaoliqaq/autocoder/ui_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.00054 | $0.01010 |
| Opus 5 | $0.00027 | $0.00505 |
| Sonnet 5 | $0.00011 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
ui-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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Design System
This skill focuses on making existing UI look production-quality. It is about visual polish, not feature building.
When To Use
Use when the subtask involves:
- Making an existing screen look better / more polished
- Enforcing visual consistency across screens
- Fixing layout issues, spacing, or color problems
- Adding micro-interactions and transitions
- Redesigning or beautifying a component/page
Approach: Audit -> Fix -> Verify
Step 1: Visual Audit
Before changing anything, read the existing code and catalog issues:
VISUAL_AUDIT:
- [ ] Inconsistent spacing (e.g., some cards use p-4, others p-6)
- [ ] Color palette violations (random hex values instead of theme tokens)
- [ ] Typography inconsistency (mixed font sizes without hierarchy)
- [ ] Missing states (loading, empty, error)
- [ ] Broken responsive layout at specific breakpoints
- [ ] Accessibility gaps (missing labels, low contrast)
- [ ] Alignment issues (text/icons not vertically centered)
- [ ] Clutter (too many visual elements competing for attention)
Step 2: Design Hierarchy
Apply the visual hierarchy pyramid to every screen:
Level 1 (most prominent): Primary action / key metric / hero content
Level 2 (secondary): Navigation / section headers / supporting data
Level 3 (tertiary): Metadata / timestamps / helper text
Level 4 (background): Borders / dividers / surface colors
Rules:
- Only 1 primary action per viewport
- Reduce visual weight as hierarchy level increases
- Use size, weight, and color to create hierarchy (not decoration)
Step 3: The 5 Polish Passes
Execute these passes in order:
Pass 1: Spacing & Alignment
- Enforce 8px grid (4px for tight UI)
- Consistent padding within component types
- Align text baselines and icon centers
- Equal gap between sibling elements
Pass 2: Color & Contrast
- Max 5 colors on any screen (neutral + primary + 2-3 semantic)
- Background layers:
white -> gray-50 -> gray-100(max 3 levels) - Text:
gray-900primary,gray-600secondary,gray-400disabled - Remove any hardcoded hex colors — use theme tokens
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 · 128 lines · 54 tokens per session scan A 9f919609ab7b
ui-design-system is a skill published in the GitHub repository qinghaoliqaq/AutoCoder (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,010 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-30.
Other skills, from other repositories
web-design
Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.
penguin-harness-frontend
Use when changing the PenguinHarness Web App (packages/web) — adding or restyling any UI, picking a status colour, adding an icon, laying out a row or a form field, writing user-facing copy, or building a popup. Covers the semantic tone tokens, the icon size/stroke/gap scale, the semantic-versus-formatting rule for…
ui-craft
Design, build, redesign, or modify browser-visible web interfaces with product-quality composition, visual systems, interaction states, responsive behavior, accessibility, and browser visual QA. Use for HTML, CSS, JavaScript, React, Vue, or Svelte pages and components, landing pages, dashboards, admin tools, settings…
frontend-design
Guidance for distinctive, intentional visual design when building or reshaping UI, HTML/React artifacts, dashboards, charts, and visual reports. Use before implementation to choose a content-specific structure, typography, and visual system that does not read as a templated default.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…