ux-analyzer

ux-analyzer is an agent for coding agents from drobins25/craft. It costs 222 tokens per session (2,847 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
Use it to review web pages, user flows, and interface code for usability, cognitive load, interaction friction, and accessibility issues.
Why use it?
It helps find confusing interactions, unnecessary effort, accessibility gaps, and other problems that developers may miss while implementing the interface.

Agent

Part of the craft plugin — 29 commands, 27 agents, 1 MCP server shipped together

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.

agentmods
npx agentmods add agents/drobins25/craft/ux-analyzer
Clone the repo
git clone --depth 1 https://github.com/drobins25/craft

Or install craft, the plugin that ships this one along with the rest of its 29 commands, 27 agents, 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.

agentmods badge for ux-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/drobins25/craft/ux-analyzer.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.svg" alt="Measured on agentmods" 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,847 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00222 $0.02847
Opus 5 $0.00111 $0.01424
Sonnet 5 $0.00044 $0.00569
Haiku 4.5 $0.00022 $0.00285

Measured 3d ago against content hash b709f31e71df, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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:

  1. Try list_pages via chrome-devtools MCP
  2. 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)
  3. 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."
  4. 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."
  5. 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.

Nielsen's 10 Usability Heuristics

Your primary evaluation framework:

1. Visibility of System Status

The system should always keep users informed about what is going on.

✓ Good signs:

  • Loading indicators for async actions
  • Progress bars for multi-step processes
  • Success/error feedback after actions
  • Current state clearly visible (logged in, selected, etc.)

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.

  1. 3d 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 (53 stars, last pushed 4d ago), licensed MIT. It adds 222 tokens to every session and 2,847 once invoked, about $0.0011 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.

Related

Other agents, from other repositories

refactor-expert

Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.

alirezarezvani/claude-code-tresor · 34 tokens

security-auditor

Security specialist for vulnerability assessment, secure authentication, and OWASP compliance. Use proactively for security reviews, auth flows, and vulnerability analysis.

alirezarezvani/claude-code-tresor · 32 tokens

performance-tuner

Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.

alirezarezvani/claude-code-tresor · 30 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

root-cause-analyzer

Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.

alirezarezvani/claude-code-tresor · 43 tokens

systems-architect

Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.

alirezarezvani/claude-code-tresor · 33 tokens