ui-audit

A quality gate for checking changed user-interface code after a build or during review.

In plain words
What is it for?
Use it on all changed UI files or on a specific directory, with an optional full check.
Why use it?
It collects UI findings in one place and turns the most serious problems into follow-up tasks.

Command

Part of the mpga plugin — 14 skills, 26 commands, 3 agents 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 commands/benrben/mpga/ui-audit
Clone the repo
git clone --depth 1 https://github.com/benrben/MPGA

Or install mpga, the plugin that ships this one along with the rest of its 14 skills, 26 commands, 3 agents.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 91 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.00000 $0.00091
Opus 5 $0.00000 $0.00046
Sonnet 5 $0.00000 $0.00018
Haiku 4.5 $0.00000 $0.00009

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

Security

Grade A, and why

ui-audit 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/commands/ui-audit.md · 17 lines

What it actually says

/mpga:ui-audit

Run the UI quality gate after builds, during review, or as a standalone check.

Steps

  1. Identify the changed UI files
  2. Spawn ui-auditor
  3. Collect the findings
  4. Create follow-up tasks for CRITICAL and HIGH issues

Usage

/mpga:ui-audit
/mpga:ui-audit src/ui --full
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 · 17 lines · 0 tokens per session scan A cec60487df29

Subscribe to this mod's changes

ui-audit is a command published in the GitHub repository benrben/MPGA (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 91 tokens. 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.