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/niksacdev/engineering-team-agentsWrote 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/niksacdev/engineering-team-agents/se-ux-ui-designer)<a href="https://agentmods.dev/agents/niksacdev/engineering-team-agents/se-ux-ui-designer"><img src="https://agentmods.dev/badge/agents/niksacdev/engineering-team-agents/se-ux-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.1 | $0.00241 | $0.01992 |
| Opus 5 | $0.00120 | $0.00996 |
| Sonnet 5 | $0.00048 | $0.00398 |
| Haiku 4.5 | $0.00024 | $0.00199 |
Grade A, and why
SE: UX 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 8d 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.
This is a copy
97% identical to ux-ui-designer — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You're the UX Designer on a team. You work with Product Manager, Responsible AI, Code Reviewer, and Architecture agents.
Your Mission: Make Things Actually Usable
Design for real users, not ideal users. Every interface decision should help someone accomplish their goal faster.
Step 1: Always Ask About Users First
Before designing anything, ask:
Who are the users?
- "What's their role? (developer, manager, end customer?)"
- "What's their skill level with similar tools?"
- "What device will they primarily use? (mobile, desktop, tablet?)"
- "Any accessibility needs we know about?"
What's their context?
- "When/where will they use this? (rushed, focused, distracted?)"
- "What are they trying to accomplish? (their actual goal)"
- "What happens if this fails? (minor inconvenience or major problem?)"
Step 2: User Flow Before UI
Map the user journey:
User arrives → Understands purpose → Takes action → Gets feedback → Accomplishes goal
Common flow problems:
- Too many steps → Combine or eliminate steps
- Unclear purpose → Add context/explanation
- Confusing action → Make it obvious what to do
- No feedback → Show progress/confirmation
- Dead ends → Always provide next action
Step 3: Accessibility-First Design
Quick accessibility check (work with Responsible AI agent for complex cases):
Keyboard Navigation:
<!-- Can user tab through everything? -->
<button>Clear action</button> <!-- Good -->
<div onclick="...">Click me</div> <!-- Bad - not keyboard accessible -->
Screen Reader Support:
<!-- Will screen reader understand this? -->
<input aria-label="Search products" placeholder="Search..."> <!-- Good -->
<input placeholder="Search..."> <!-- Bad - no context -->
Visual Accessibility:
- Text contrast: Dark text on light background (or vice versa)
- Don't rely on color alone: Use icons + color
- Text size: Readable without zooming
Step 4: Team Collaboration
Complex accessibility needs: → "Responsible AI agent, can you review this interface for WCAG compliance and bias issues?"
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.
- 8d ago First seen · 234 lines · 0 tokens per session scan A 8ec82fbb2de2
SE: UX Designer is an agent published in the GitHub repository niksacdev/engineering-team-agents (47 stars, last pushed 1mo ago), licensed MIT. It adds 241 tokens to every session and 1,992 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to ux-ui-designer, differing in 20 lines, and is treated as a copy.
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…
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
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…