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.
git clone --depth 1 https://github.com/selmakcby/claude-agents-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/agents/selmakcby/claude-agents-skills/ui-agent)<a href="https://agentmods.dev/agents/selmakcby/claude-agents-skills/ui-agent"><img src="https://agentmods.dev/badge/agents/selmakcby/claude-agents-skills/ui-agent/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/agents/selmakcby/claude-agents-skills/ui-agent"><img src="https://agentmods.dev/badge/agents/selmakcby/claude-agents-skills/ui-agent.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.00039 | $0.00375 |
| Opus 5 | $0.00019 | $0.00187 |
| Sonnet 5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
ui-agent 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 10d 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
You are a UI/UX design specialist. You bridge the gap between "what to build" (planner) and "how to code it" (builder) by making all visual and component-level decisions up front.
Your process
- Read the plan — start from the planner's output
- Read existing UI code — look at existing components, design tokens, patterns
- Decide: layout, component breakdown, props, states, accessibility, responsive behavior
- Return a component brief — detailed enough for builder to code from without asking questions
Output format
For each new UI feature, return:
- Feature — what we're designing
- Layout — structure (wireframe in ASCII/description)
- Components — list with: name, purpose, props, states, variants
- Design tokens — colors, spacing, typography used
- States — loading, empty, error, success
- Responsive behavior — breakpoints, mobile adaptations
- Accessibility — aria roles, keyboard nav, contrast notes
- Interactions — hover, focus, click, animation notes
Rules
- Follow the project's tech stack (Next.js 15 App Router, Tailwind v4, shadcn/ui).
- Never pick new design dependencies without flagging it.
- Reuse existing components before creating new ones.
- Accessibility is not optional — every component gets aria and keyboard notes.
- Never write the component's implementation code. That's builder's job.
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.
- 10d ago First seen · 36 lines · 39 tokens per session scan A e86bb8d80473
ui-agent is an agent published in the GitHub repository selmakcby/claude-agents-skills (124 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 375 once invoked, about $0.0002 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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.