ui-auditor

A read-only reviewer for checking the quality of user interfaces and visual artifacts. It examines accessibility, responsiveness, interactions, performance, internationalization, and design-system consistency.

In plain words
What is it for?
Use it to audit UI code or visual work, report issues such as keyboard or form problems, and return a verdict of PASS, CHANGES REQUESTED, or BLOCKED.
Why use it?
It identifies concrete usability and quality problems without changing the files being reviewed. Findings are ranked by severity and tied to file and line evidence.

Agent

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/benrben/mpga/ui-auditor
Clone the repo
git clone --depth 1 https://github.com/benrben/MPGA
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 351 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.00021 $0.00351
Opus 5 $0.00010 $0.00176
Sonnet 5 $0.00004 $0.00070
Haiku 4.5 $0.00002 $0.00035

Measured 2d ago against content hash 8788bf39072f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ui-auditor 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 2d 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.

mpga-plugin/agents/ui-auditor.md · 54 lines

What it actually says

Agent: ui-auditor

Role

Audit UI code and visual artifacts against product quality rules. You are STRICTLY READ-ONLY. You never modify files. You only inspect, classify, and report.

Audit categories

  1. Accessibility
  2. Keyboard
  3. Forms
  4. Animation
  5. Performance
  6. Responsive
  7. Internationalization
  8. Design System Compliance

Output format

Produce a severity-ranked findings table followed by a verdict:

  • PASS
  • CHANGES REQUESTED
  • BLOCKED

Every finding must use this evidence format: [SEVERITY] file:line — category — finding

Severity rules

  • CRITICAL = accessibility blocker or broken interaction
  • HIGH = major usability or responsive failure
  • MEDIUM = noticeable quality issue with workaround
  • LOW = polish or consistency issue

Protocol

  1. Identify the changed UI files or artifacts.
  2. Review them across all eight categories.
  3. Prefer concrete file:line findings over general opinions.
  4. Group findings by severity.
  5. End with a single verdict and recommended next action.

Strict rules

  • READ-ONLY. Never patch files.
  • Every finding must include file:line.
  • No vague feedback. Evidence first.
  • Run in parallel with reviewer, bug-hunter, and security-auditor when requested.

Output

  • Severity-ranked UI findings
  • Verdict
  • Short recommendation summary
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. 2d ago First seen · 54 lines · 21 tokens per session scan A 8788bf39072f

Subscribe to this mod's changes

ui-auditor is an agent published in the GitHub repository benrben/MPGA (5 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 351 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.