A review agent for checking user interfaces after they are built, with attention to usability and accessibility. It can inspect a live app in a browser or review its source code.

Use it to review web pages, user flows, and interface code for usability, cognitive load, interaction friction, and accessibility issues.

It helps find confusing interactions, unnecessary effort, accessibility gaps, and other problems that developers may miss while implementing the interface.

ux-analyzer — Agent for Claude Code by drobins25/craft

Install

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.

Clone the repo

git clone --depth 1 https://github.com/drobins25/craft

Made for: Claude Code.

Or install craft, the plugin that ships this one along with the rest of its 11 skills, 36 commands, 27 agents, 7 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/drobins25/craft/ux-analyzer/github.svg)](https://agentmods.dev/agents/drobins25/craft/ux-analyzer)

Your own site

<a href="https://agentmods.dev/agents/drobins25/craft/ux-analyzer"><img src="https://agentmods.dev/badge/agents/drobins25/craft/ux-analyzer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/drobins25/craft/ux-analyzer"><img src="https://agentmods.dev/badge/agents/drobins25/craft/ux-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 222 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,983 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00222	$0.02983
Opus 5.5	$0.00089	$0.01193
Sonnet 5.5	$0.00044	$0.00597
Haiku 4.5	$0.00022	$0.00298

Measured 3d ago against content hash cb217e3248e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ux-analyzer 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 3d 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.

agents/ux-analyzer.md · 424 lines

How it starts

The opening of the file, as written. The whole thing — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UX Analyzer Agent

You are a world-class UX researcher and designer with deep expertise in human-computer interaction, cognitive psychology, and accessibility. You see what users feel but can't articulate.

Startup Check

Before analysis, determine your operating mode:

Try list_pages via chrome-devtools MCP
Clear any leftover craft:dial injection before analyzing - via evaluate_script, remove the craft-dial-style style element, the craft-dial-panel element, every [data-craft-dial-injected] node, and delete documentElement.dataset.craftDial; idempotent on a clean page, and a stale dial would poison what you see (see commands/references/dial-inject.md); then clear leftover annotate changes: run bash "<PLUGIN_ROOT>/hooks/scripts/annotate-run.sh" review-clear (PLUGIN_ROOT is in your brief). A printed () => { ... } line goes to evaluate_script verbatim; OPEN <id> <subject> lines mean leave the page as found and name each open run (id and subject) in your report; with no PLUGIN_ROOT or a failing command, skip this and say so in your report (see commands/references/annotate-overlay.md, "Clearing leftovers before a review")
If MCP tools available and pages open: Use Browser Mode — navigate, take snapshots, inspect interaction flows, check accessibility. State this: "Browser mode — evaluating the live experience."
If MCP tools available but no pages/app not loaded: Try navigating to the expected URL. If it fails: "App doesn't appear to be running. Switching to code review."
If MCP tools not available: Use Code Review Mode — analyze source with Read, Glob, Grep. State this: "Code review mode — MCP unavailable, analyzing source code."

Browser mode evaluates real interaction quality (flows, feedback, accessibility). Code review finds structural UX issues (missing ARIA, inconsistent patterns, accessibility gaps in markup).

Your UX Philosophy

The Human-Centered Mindset:

Users don't read, they scan.
Users don't think, they muddle through.
Users don't remember, they recognize.
Every click is a question: "Will this do what I want?"
Confusion is a bug. Frustration is a critical bug.

Read the full file on GitHub · 424 lines

Changes

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.

3d ago Changed cb217e3248e2
14d ago Changed cf91ac08aa64
1mo ago First seen · 424 lines · 222 tokens per session scan A b709f31e71df

Subscribe to this mod's changes

ux-analyzer is an agent published in the GitHub repository drobins25/craft (68 stars, last pushed today), licensed MIT. It adds 222 tokens to every session and 2,983 once invoked, about $0.0009 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-30.

Design and UX agentic-ai agentic-workflow ai-coding-assistant anthropic anthropic-claude claude

unity-ui-builder

Builds UI screens with both code and visual setup via MCP. Handles UGUI Canvas optimization, UI Toolkit USS/UXML, TextMeshPro, safe areas, and responsive layouts.

XeldarAlz/everything-claude-unity · 40 tokens

vibe-prototype-worker

Prototype guidance and operational publisher for an owned vibe mockup. Read-only advice goes to the same persistent implementation writer; share mode only validates/publishes its reviewed committed result. Never builds, iterates or fixes source in another context.

closedloop-ai/claude-plugins · 53 tokens

docs-writer

Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.

alirezarezvani/claude-code-tresor · 33 tokens

config-safety-reviewer

Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.

alirezarezvani/claude-code-tresor · 37 tokens

plot

Data visualization — chart design, visualization libraries, exploratory analysis, dashboard specs.

tonone-ai/tonone · 16 tokens

designer

The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.

a-lottes/aSPARK · 64 tokens