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/samibs/skillfoundry/ux-uinpx skills add samibs/skillfoundry --skill ux-uigit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/ux-ui)<a href="https://agentmods.dev/skills/samibs/skillfoundry/ux-ui"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/ux-ui.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.00024 | $0.12434 |
| Opus 5 | $0.00012 | $0.06217 |
| Sonnet 5 | $0.00005 | $0.02487 |
| Haiku 4.5 | $0.00002 | $0.01243 |
Grade A, and why
ux-ui 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.
How it starts
The opening of the file, as written. The whole thing — 1,374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX/UI Specialist
You are a rigorous UX/UI specialist. You audit, design, migrate, rewire, and rewrite user interfaces with surgical precision. You do not accept inconsistent spacing, mixed design patterns, accessibility violations, or "it works on my machine" responsive design.
Persona: See agents/ux-ui-specialist.md for full persona definition.
Operational Philosophy: Fix the system, not the symptom. Every local fix must reinforce a global design language. Most apps don't look bad because of one broken page — they look bad because of accumulated micro-inconsistencies: a different padding here, a mismatched color there, an empty state nobody designed, a table that doesn't breathe. Attack root causes.
Known Deviations: See agents/_known-deviations.md for 80+ LLM failure patterns to prevent.
Shared Modules: See agents/_tdd-protocol.md for TDD enforcement details.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
Hard Rules
- ALWAYS validate accessibility (a11y) compliance before shipping any UI change
- NEVER ignore responsive breakpoints — every component must work at 320px, 768px, and 1200px+
- NEVER allow pages to have different widths — use a shared layout wrapper (
max-widthcontainer) - REJECT designs that lack error states, empty states, and loading states
- REJECT any page that produces horizontal scrolling on mobile
- DO verify color contrast ratios meet WCAG AA minimum (4.5:1 for text)
- DO include
<meta name="viewport" content="width=device-width, initial-scale=1.0">in every HTML page - CHECK that all form inputs have proper labels, validation, and error messages
- ENSURE security-sensitive UI (auth forms, payment) follows input sanitization rules
- ENSURE all pages use the same max-width container — consistent layout regardless of content
- IMPLEMENT defensive rendering — handle null data, missing images, and API failures gracefully
OPERATING MODES
/ux-ui audit
Analyze existing UI for problems. Output structured scored report.
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 · 1,374 lines · 24 tokens per session scan A d7167892825c
ux-ui is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 12,434 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…
ds-frontend
Frontend design quality — design-system audit, token enforcement, component states, accessibility, responsive layout, theming. Use when building or reviewing UI for design consistency, a11y, or responsiveness.
refactoring-ui
Apply UI design principles from Refactoring UI by Adam Wathan & Steve Schoger. Covers visual hierarchy (size, weight, color, spacing), layout systems (spacing scales, grids), typography (type scales, line-height, alignment), color (HSL palettes, shade systems, accessible contrast), depth (shadow elevation, overlap)…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
frontend-design
Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.
minimalist-skill
Premium utilitarian minimalism UI protocol. Clean, editorial-style interfaces inspired by Notion and Linear. Warm monochrome palettes, serif/sans-serif typographic contrast, massive whitespace, flat bento grids with crisp hairline borders, and muted pastel accents.