ui-review

ui-review is a command for Claude Code from Oriolshhh/runware-image-mcp. It costs 29 tokens per session (331 once invoked), scanned A, original, MIT.

A command for reviewing user-facing interface changes for ease of use, accessibility, and consistency across different screen sizes and states.

In plain words
What is it for?
Use it to inspect screens or components and get prioritized fixes for accessibility, responsive layout, interaction states, and visual consistency.
Why use it?
It catches problems with keyboard use, focus, readable contrast, forms, loading, errors, and other situations that can prevent people from using an interface.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to inspect screens or components and get prioritized fixes for accessibility, responsive layout, interaction states, and visual consistency.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/oriolshhh/runware-image-mcp/ui-review
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/Oriolshhh/runware-image-mcp

Made for: Claude Code.

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 ui-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/ui-review/github.svg)](https://agentmods.dev/commands/oriolshhh/runware-image-mcp/ui-review)
Your own site
<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/ui-review"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/ui-review/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.

agentmods 80×15 button for ui-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/ui-review"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/ui-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 331 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00331
Opus 5 $0.00015 $0.00166
Sonnet 5 $0.00006 $0.00066
Haiku 4.5 $0.00003 $0.00033

Measured 9d ago against content hash 326b0e770987, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ui-review 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.

.agent/commands/ui-review.md · 50 lines

What it actually says

/ui-review — Actionable UX and accessibility review

Purpose

Make user-facing changes accessible, usable, and consistent.

Invocation

/ui-review <screen or component>

Accepted input

The UI change and any design system in use.

Prerequisites

A user-facing change to review.

Procedure

  1. Check accessibility: semantic HTML, ARIA, keyboard and focus order, contrast.
  2. Verify loading, empty, error, and success states.
  3. Check forms: labels, validation, and error recovery.
  4. Assess hierarchy, spacing, responsiveness, and design-system consistency.
  5. Separate blocking issues from polish; give each a concrete remediation.

Approval points

None; output feeds /fix.

Expected output

A prioritized list of blocking issues and polish, each with a fix.

Failure behavior

If the UI cannot be exercised, report what is missing and stop.

Completion checks

  • Exercise keyboard, focus, accessible names, contrast, zoom/responsiveness, reduced motion, forms, and relevant asynchronous states.
  • Every blocking issue names the affected component, reproduction path, user impact, and concrete remediation; cite WCAG where applicable.
  • Record untested environments or assistive technologies instead of implying complete coverage.

Agents and skills

Agent: ux-reviewer. Skill: ui-review.

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. 9d ago First seen · 50 lines · 29 tokens per session scan A 326b0e770987

Subscribe to this mod's changes

ui-review is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 331 once invoked, about $0.0001 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.