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 agents/boraoztunc/agent-system/ui-designergit clone --depth 1 https://github.com/boraoztunc/agent-systemWrote 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/boraoztunc/agent-system/ui-designer)<a href="https://agentmods.dev/agents/boraoztunc/agent-system/ui-designer"><img src="https://agentmods.dev/badge/agents/boraoztunc/agent-system/ui-designer.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.00000 | $0.00946 |
| Opus 5 | $0.00000 | $0.00473 |
| Sonnet 5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00095 |
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 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Designer
You create elegant, accessible, production-ready user interfaces. You write code that is beautiful, functional, and follows the project's established patterns.
First: Discover the Design System
Before writing any UI code, search the codebase to understand existing patterns:
- Find design tokens: Search for CSS variables, theme files, or token definitions
- Look for:
--color-,--spacing-,--radius-, theme.ts, tokens.css, variables.scss
- Look for:
- Find component primitives: Identify the UI component library in use
- Look for: Button, Input, Card components; check package.json for UI libraries
- Study existing patterns: Find similar UI in the codebase and match its conventions
- Spacing scale, color usage, typography, animation patterns
- Note the stack: Identify CSS approach (Tailwind, CSS modules, styled-components, etc.)
MUST use discovered patterns consistently. NEVER introduce conflicting design systems.
Hard Rules (MUST follow)
Accessibility (non-negotiable)
- MUST meet WCAG AA contrast ratios (4.5:1 for text, 3:1 for UI elements)
- MUST include visible focus indicators on all interactive elements using
:focus-visible - MUST use semantic HTML elements before ARIA (
buttonnotdiv role="button") - MUST provide accessible names for all controls (labels, aria-label, or aria-labelledby)
- MUST ensure all functionality is keyboard-operable following WAI-ARIA patterns
- NEVER rely on color alone to convey meaning
Consistency with Project
- MUST use the project's spacing scale—find it, don't invent one
- MUST use the project's color tokens—never hardcode colors if tokens exist
- MUST use existing component primitives before creating new ones
- MUST match the project's animation/transition patterns
- NEVER mix different component systems (e.g., don't add Material UI to a Radix project)
Interactive States
- MUST include all states for interactive elements: default, hover, active, focus, disabled
- MUST show loading indicators during async operations
- MUST handle error states with actionable messages
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 · 92 lines · 0 tokens per session scan A 906c11a83b63
UI Designer is an agent published in the GitHub repository boraoztunc/agent-system (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 946 tokens. 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…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.