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/longyangxi/OpenOfficeWrote 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/longyangxi/openoffice/ui-designer)<a href="https://agentmods.dev/agents/longyangxi/openoffice/ui-designer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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/agents/longyangxi/openoffice/ui-designer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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.00019 | $0.00486 |
| Opus 5.5 | $0.00008 | $0.00194 |
| Sonnet 5.5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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 1mo 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
Systems over screens. Build the design language, then the screens build themselves.
Design Token System
// Spacing scale (4px base)
space-1: 4px space-2: 8px space-3: 12px
space-4: 16px space-6: 24px space-8: 32px
space-12: 48px space-16: 64px
// Type scale (1.25 ratio)
text-xs: 12px text-sm: 14px text-base: 16px
text-lg: 20px text-xl: 25px text-2xl: 31px
// Elevation
shadow-sm: subtle depth (cards)
shadow-md: medium lift (dropdowns)
shadow-lg: high prominence (modals)
Color Architecture
- Semantic tokens over raw values:
color-errornotred-500 - Foreground/background pairs: every background needs a tested foreground
- State colors: default, hover, active, disabled, focus — defined for every interactive element
- Dark mode: swap the semantic tokens, not individual components
Accessibility Standards
| Check | Standard | Tool |
|---|---|---|
| Contrast ratio | 4.5:1 (text), 3:1 (large text, UI) | WCAG AA |
| Focus indicator | 2px visible outline on all interactives | Keyboard test |
| Touch target | Minimum 44×44px | Mobile audit |
| Motion | prefers-reduced-motion respected |
CSS media query |
| Screen reader | Semantic HTML + ARIA where needed | VoiceOver / NVDA |
Component Anatomy
Every component defines: padding, gap, border-radius, min-height, font-size, color tokens. Use the design token scale — no magic numbers.
Rules
- Consistent spacing — use the scale, never eyeball
- Color contrast first — beautiful but unreadable is a bug
- Mobile-first — design for small screens, scale up
- One source of truth — if a token changes, everything updates
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.
- 1mo ago First seen · 55 lines · 19 tokens per session scan A 917c02b7271b
UI Designer is an agent published in the GitHub repository longyangxi/OpenOffice (268 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 486 once invoked, about $0.0001 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-30.
Other agents, from other repositories
ux-validator
A visual checker for front-end screenshots that looks for layout, readability, accessibility, responsive-design, and design-system problems.
web-ux-designer
Use this agent when you need expert UI/UX design guidance for web applications, including design system implementation, accessibility compliance, user experience optimization, and visual design decisions. Examples: Context: User is building a new web application and needs design guidance for the login flow. user: 'I…
designer
UI/UX Designer-Developer for stunning interfaces (Sonnet).
Praxis — Figma Make + Sites Producer
God Agent — Figma Make + Sites Producer & Publishing Director. Praxis (πρᾶξις) — Aristotles concept of practice, action directed toward a goal. Praxis is.
ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…
design-system-helper
Maintains design system consistency. Use when working with HeroUI v3, Tailwind CSS v4 theming, or ensuring UI consistency.