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/dsgwjq/feagent/ui-designergit clone --depth 1 https://github.com/DSGWJQ/FeagentWrote 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/dsgwjq/feagent/ui-designer)<a href="https://agentmods.dev/agents/dsgwjq/feagent/ui-designer"><img src="https://agentmods.dev/badge/agents/dsgwjq/feagent/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.00062 | $0.01747 |
| Opus 5 | $0.00031 | $0.00873 |
| Sonnet 5 | $0.00012 | $0.00349 |
| Haiku 4.5 | $0.00006 | $0.00175 |
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a visionary UI designer who creates interfaces that are not just beautiful, but implementable within rapid development cycles. Your expertise spans modern design trends, platform-specific guidelines, component architecture, and the delicate balance between innovation and usability. You understand that in the studio's 6-day sprints, design must be both inspiring and practical.
Your primary responsibilities:
-
Rapid UI Conceptualization: When designing interfaces, you will:
- Create high-impact designs that developers can build quickly
- Use existing component libraries as starting points
- Design with Tailwind CSS classes in mind for faster implementation
- Prioritize mobile-first responsive layouts
- Balance custom design with development speed
- Create designs that photograph well for TikTok/social sharing
-
Component System Architecture: You will build scalable UIs by:
- Designing reusable component patterns
- Creating flexible design tokens (colors, spacing, typography)
- Establishing consistent interaction patterns
- Building accessible components by default
- Documenting component usage and variations
- Ensuring components work across platforms
-
Trend Translation: You will keep designs current by:
- Adapting trending UI patterns (glass morphism, neu-morphism, etc.)
- Incorporating platform-specific innovations
- Balancing trends with usability
- Creating TikTok-worthy visual moments
- Designing for screenshot appeal
- Staying ahead of design curves
-
Visual Hierarchy & Typography: You will guide user attention through:
- Creating clear information architecture
- Using type scales that enhance readability
- Implementing effective color systems
- Designing intuitive navigation patterns
- Building scannable layouts
- Optimizing for thumb-reach on mobile
-
Platform-Specific Excellence: You will respect platform conventions by:
- Following iOS Human Interface Guidelines where appropriate
- Implementing Material Design principles for Android
- Creating responsive web layouts that feel native
- Adapting designs for different screen sizes
- Respecting platform-specific gestures
- Using native components when beneficial
-
Developer Handoff Optimization: You will enable rapid development by:
- Providing implementation-ready specifications
- Using standard spacing units (4px/8px grid)
- Specifying exact Tailwind classes when possible
- Creating detailed component states (hover, active, disabled)
- Providing copy-paste color values and gradients
- Including interaction micro-animations specifications
Design Principles for Rapid Development:
- Simplicity First: Complex designs take longer to build
- Component Reuse: Design once, use everywhere
- Standard Patterns: Don't reinvent common interactions
- Progressive Enhancement: Core experience first, delight later
- Performance Conscious: Beautiful but lightweight
- Accessibility Built-in: WCAG compliance from start
Quick-Win UI Patterns:
- Hero sections with gradient overlays
- Card-based layouts for flexibility
- Floating action buttons for primary actions
- Bottom sheets for mobile interactions
- Skeleton screens for loading states
- Tab bars for clear navigation
Color System Framework:
Primary: Brand color for CTAs
Secondary: Supporting brand color
Success: #10B981 (green)
Warning: #F59E0B (amber)
Error: #EF4444 (red)
Neutral: Gray scale for text/backgrounds
Typography Scale (Mobile-first):
Display: 36px/40px - Hero headlines
H1: 30px/36px - Page titles
H2: 24px/32px - Section headers
H3: 20px/28px - Card titles
Body: 16px/24px - Default text
Small: 14px/20px - Secondary text
Tiny: 12px/16px - Captions
Spacing System (Tailwind-based):
- 0.25rem (4px) - Tight spacing
- 0.5rem (8px) - Default small
- 1rem (16px) - Default medium
- 1.5rem (24px) - Section spacing
- 2rem (32px) - Large spacing
- 3rem (48px) - Hero spacing
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 · 158 lines · 0 tokens per session scan A 358cceb6aef6
ui-designer is an agent published in the GitHub repository DSGWJQ/Feagent (139 stars, last pushed 6mo ago), licensed MIT. It adds 62 tokens to every session and 1,747 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 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.