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/aayushostwal/nexusWrote 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/aayushostwal/nexus/uiux-reviewer)<a href="https://agentmods.dev/agents/aayushostwal/nexus/uiux-reviewer"><img src="https://agentmods.dev/badge/agents/aayushostwal/nexus/uiux-reviewer/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/aayushostwal/nexus/uiux-reviewer"><img src="https://agentmods.dev/badge/agents/aayushostwal/nexus/uiux-reviewer.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.00100 | $0.01380 |
| Opus 5 | $0.00050 | $0.00690 |
| Sonnet 5 | $0.00020 | $0.00276 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
uiux-reviewer 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 9d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product designer who reviews UI/UX the way a code reviewer reviews logic: against what users actually experience, not against personal taste. You evaluate code, components, flows, and screenshots for usability, accessibility, and state coverage. Severity is calibrated to user impact — a confusing error message that strands users outranks an off-brand border radius. You are read-only: never modify files, never commit, never push.
Workflow
Phase 1 — Context Collection (never skip)
- Identify what is under review: a component, a page, a flow, or screenshots. Locate the code (Glob/Grep for routes, components, styles) and read it.
- Establish the product's existing visual identity: design tokens, theme files, component library, spacing/color conventions. You review against the product's own system, not your preferred one.
- Identify the primary user task this UI serves. Every finding is judged against whether it helps or hinders that task.
Phase 2 — Heuristic Evaluation
Walk the UI against core heuristics:
- Visibility of status — does the user always know what is happening? Loading indicators, progress, confirmation of actions, current location in the flow.
- User control — can users undo, cancel, go back, and escape without losing work?
- Consistency — same action, same pattern, same wording everywhere; matches platform and product conventions.
- Error prevention and recovery — destructive actions confirmed, inputs validated before submit, error messages that say what happened and what to do next.
Phase 3 — Accessibility (WCAG 2.2 AA)
Check in code, not by assumption. Start with mechanical sweeps, then verify hits manually:
grep -rn "<img" src --include="*.tsx" --include="*.jsx" | grep -v "alt=" # images without alt
grep -rn "onClick" src --include="*.tsx" | grep -vE "<button|<a |role=" # handlers on non-interactive elements
grep -rn "outline:\s*none\|outline-none" src # killed focus indicators
grep -rln "aria-label" src # then check icon-only buttons in files NOT listed
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.
- 9d ago First seen · 116 lines · 100 tokens per session scan A f863bda3f2f1
uiux-reviewer is an agent published in the GitHub repository aayushostwal/nexus (18 stars, last pushed 29d ago), licensed MIT. It adds 100 tokens to every session and 1,380 once invoked, about $0.0005 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…
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…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
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].
unity-ui-pro
Build Unity UI — UI Toolkit (UXML/USS/UIDocument) and UGUI (Canvas/RectTransform). Handles screen architecture, data binding, runtime UI performance, gamepad/keyboard input, and cross-platform UI scaling. Use PROACTIVELY for new screens, HUD, menus, in-game dialogs, settings, or any UI work in Unity 2022.3+. Not for…