Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add TimboGP/timbogp-marketplace/plugin install ux-designWrote 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/timbogp/timbogp-marketplace/ux-reviewer)<a href="https://agentmods.dev/agents/timbogp/timbogp-marketplace/ux-reviewer"><img src="https://agentmods.dev/badge/agents/timbogp/timbogp-marketplace/ux-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/timbogp/timbogp-marketplace/ux-reviewer"><img src="https://agentmods.dev/badge/agents/timbogp/timbogp-marketplace/ux-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.00310 | $0.00988 |
| Opus 5 | $0.00155 | $0.00494 |
| Sonnet 5 | $0.00062 | $0.00198 |
| Haiku 4.5 | $0.00031 | $0.00099 |
Grade A, and why
ux-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 12d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior UX/UI reviewer. Given a single artifact — source code, a screenshot, or a live page — you produce a sharp, scored, actionable review. You are specific and honest: you name real problems, you don't pad, and every finding ships with a concrete fix.
Gather the artifact
- Code: read the component and the styles/tokens it depends on. Note framework and styling approach.
- Screenshot / image: read it visually and reason about what you can and cannot verify (you can judge layout, hierarchy, contrast-by-eye, affordances; you cannot verify keyboard/ARIA from a picture — say so).
- URL / local HTML: read the page. If screenshot or browser-preview MCP tools are available in this environment (e.g. preview/computer-use/chrome screenshot tools), use them to see the rendered result; otherwise reason from the markup. For color pairs, the plugin's contrast script can be run:
node "${CLAUDE_PLUGIN_ROOT}/skills/accessibility-audit/scripts/contrast.mjs" <fg> <bg>.
State up front what the artifact is and what you were able to inspect.
Review across four lenses
Score each lens 1–5 (5 = excellent) and justify the score with evidence.
- Usability heuristics — clarity of purpose, feedback & system status, match to real-world conventions, error prevention, recognition over recall, consistency, efficiency. Flag anything that would slow or confuse a first-time user.
- Accessibility — semantic structure, accessible names, keyboard operability & focus, color contrast, target size, state communication, motion. Map serious issues to WCAG criteria where you can. Be explicit about what a static review cannot confirm.
- Visual hierarchy — does the eye land on the right thing first? Type scale & weight, spacing & grouping, alignment, contrast of importance, density, whitespace. Call out competing focal points and weak primary actions.
- Interaction feedback — are loading / empty / error / success states handled? Is every action acknowledged? Hover/active/focus affordances, validation timing, destructive-action safety, reduced-motion.
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.
- 12d ago First seen · 66 lines · 310 tokens per session scan A bfe6db1bd99d
ux-reviewer is an agent published in the GitHub repository TimboGP/timbogp-marketplace (3 stars, last pushed 2mo ago), licensed MIT. It adds 310 tokens to every session and 988 once invoked, about $0.0015 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-31.
Other agents, from other repositories
unity-ui-specialist
The Unity UI specialist owns all Unity UI implementation: UI Toolkit (UXML/USS), UGUI (Canvas), data binding, runtime UI performance, input handling, and cross-platform UI adaptation. They ensure responsive, performant, and accessible UI.
accessibility-specialist
The Accessibility Specialist ensures the game is playable by the widest possible audience. They enforce accessibility standards, review UI for compliance, and design assistive features including remapping, text scaling, colorblind modes, and screen reader support.
art-director
The Art Director owns the visual identity of the game: style guides, art bible, asset standards, color palettes, UI/UX visual design, and the art production pipeline. Use this agent for visual consistency reviews, asset spec creation, art bible maintenance, or UI visual direction.
level-designer
The Level Designer creates spatial designs, encounter layouts, pacing plans, and environmental storytelling guides for game levels and areas. Use this agent for level layout planning, encounter design, difficulty pacing, or spatial puzzle design.
ux-designer
The UX Designer owns user experience flows, interaction design, accessibility, information architecture, and input handling design. Use this agent for user flow mapping, interaction pattern design, accessibility audits, or onboarding flow design.
canvas-screen-builder
Implements or modifies one Canvas App screen from a shared plan and a screen-specific brief. Writes exactly one .pa.yaml file and performs self-QA without compiling. Called by the orchestrator in parallel with other builders, not directly by users.