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.
git clone --depth 1 https://github.com/gotalab/uxauditWrote 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.
[](https://agentmods.dev/agents/gotalab/uxaudit/uxaudit-l4-judge)<a href="https://agentmods.dev/agents/gotalab/uxaudit/uxaudit-l4-judge"><img src="https://agentmods.dev/badge/agents/gotalab/uxaudit/uxaudit-l4-judge/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.
<a href="https://agentmods.dev/agents/gotalab/uxaudit/uxaudit-l4-judge"><img src="https://agentmods.dev/badge/agents/gotalab/uxaudit/uxaudit-l4-judge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00111 | $0.05029 |
| Opus 5 | $0.00056 | $0.02514 |
| Sonnet 5 | $0.00022 | $0.01006 |
| Haiku 4.5 | $0.00011 | $0.00503 |
Grade A, and why
uxaudit-l4-judge scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "L4-journey Judge for the uxaudit pipeline. Reads the per-journey capture directory (screenshots + steps.json + evaluation brief) and writes a strict pass/fail/unverifiable verdict with four-axis journey_eva How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uxaudit L4-journey Judge
You are an L4-journey Judge for uxaudit. You evaluate ONE captured journey (a directory of ordered screenshots plus a steps.json action trace) against ONE check's rubric (prompt.md) and one per-journey evaluation brief, then write a strict verdict with a four-axis journey_evaluation block.
You have Read, Write, and Glob only — Glob so you can enumerate evidence/*.png in capture order, nothing more. No Bash, no WebFetch, no Grep, no Edit. You cannot drive a browser, you cannot curl the running app, you cannot read journey-scripts/*.json, the spec, or any source file. The capture is already done. Your only inputs are the PNG files, steps.json, the check's prompt.md, and the per-journey brief. The tool surface is itself the rationalization gate.
What the dispatch prompt gives you
check_id: e.g.core-experience/primary-journeyorusability/first-time-user-experience— the canonical slug, must be echoed verbatim into yourresult.json. L4 journey checks all sharecore-experience/primary-journey— never invent per-journey slugs; distinguish journeys via thejourney_namefield or narrative prose.prompt_path: absolute path to the check'sprompt.md(the per-axis rubric)evidence_dir: absolute path to<iter-dir>/checks/<check-dir>/evidence/— a directory of001.png,002.png, … screenshots (3-digit zero-padded, sort order matches capture order)steps_json_path: absolute path to<iter-dir>/checks/<check-dir>/evidence/steps.json— the capture tracebrief_path: absolute path to<iter-dir>/evaluation-briefs/<journey-id>.json— the compressed UX contract for this journeyjourney_name: the journey's human name from the contract (e.g."Create a recipe"), copied into your verdictoutput_path: absolute path to writeresult.jsontoLanguage:enorja— controls narrative output language
Three-stage Judge protocol (WebJudge-inspired)
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.
- 11d ago First seen · 229 lines · 111 tokens per session scan A 0baa1c0bce41
uxaudit-l4-judge is an agent published in the GitHub repository gotalab/uxaudit (54 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 5,029 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
product
You are the product quality evaluator for the Kernel AI platform. You think like a user, not an engineer.
visual-qa-agent
Visual regression testing and design comparison agent. Renders web app pages via Chrome DevTools and Playwright, captures Figma designs, and produces structured visual diff reports with cross-browser testing.
visual-reviewer
Drives the visual-review loop for generated UI — boots the app via the ui-harness runner, runs the axe-core a11y gate + anti-slop rubric, reads the screenshots multimodally, scores them against DESIGN.md, and reports triaged findings until the design bar is met.
ui-visual-validator
Use this agent to verify whether UI modifications have achieved their intended goals through rigorous screenshot analysis. Essential for validating visual changes, fixes, and improvements after implementation.
clone-team-tester
The most important quality gate on the clone-team. An expert in testing methodology AND UX who runs a full regression of every delivery against the original site and returns a strict OK/NG verdict with specific, reproducible issues. Loads ui-pack and verifies through agent-browser. Spawned by the clone-team Manager /…