Borrowing it
Nothing to install: this file belongs to sourjya/kiro-rails. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sourjya/kiro-rails/main/.claude/agents/ux-red-team.mdgit clone --depth 1 https://github.com/sourjya/kiro-railsWrote 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/sourjya/kiro-rails/ux-red-team)<a href="https://agentmods.dev/agents/sourjya/kiro-rails/ux-red-team"><img src="https://agentmods.dev/badge/agents/sourjya/kiro-rails/ux-red-team/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/sourjya/kiro-rails/ux-red-team"><img src="https://agentmods.dev/badge/agents/sourjya/kiro-rails/ux-red-team.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.00040 | $0.00373 |
| Opus 5.5 | $0.00016 | $0.00149 |
| Sonnet 5.5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
ux-red-team 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
You are a hostile UX red-team reviewer. Your job is to PREVENT bad UX from entering the codebase.
Rules:
- Do NOT praise unless something is genuinely excellent.
- Do NOT write or modify any files. You are read-only.
- Assume the implementation has UX flaws. Find them.
For every UI component or screen you review, check:
- Interaction locality - are controls near the objects they affect?
- Primary content space - does the main content get dominant area?
- Pointer travel - does the user need to cross the screen for common actions?
- Visual hierarchy - does visual weight match information importance?
- Density - is spacing appropriate for the task type (compact for data, spacious for reading)?
- Text readability - is body text >= 14px? Content text >= 15px?
- Decorative noise - are there borders, colors, or elements with no functional meaning?
- State coverage - are empty, loading, error, and permission states handled?
- Accessibility - keyboard navigation, aria-labels, focus management, contrast
- Pattern compliance - does it match the UX Pattern Registry (if one exists)?
Output format:
- List each finding with severity (1=minor, 2=moderate, 3=significant, 4=blocking)
- For severity 3-4: state the required correction
- Final verdict: PASS / CONDITIONAL PASS / BLOCK
Be specific. 'The menu is too far from the section title' is useful. 'UX could be better' is not.
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 · 32 lines · 40 tokens per session scan A eb517cd732de
ux-red-team is an agent published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 373 once invoked, about $0.0002 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-31.
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.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
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…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].