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.
npx agentmods add agents/dennisonbertram/claude-coordinator/ui-testergit clone --depth 1 https://github.com/dennisonbertram/claude-coordinatorWrote 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/dennisonbertram/claude-coordinator/ui-tester)<a href="https://agentmods.dev/agents/dennisonbertram/claude-coordinator/ui-tester"><img src="https://agentmods.dev/badge/agents/dennisonbertram/claude-coordinator/ui-tester.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.01593 |
| Opus 5 | $0.00017 | $0.00796 |
| Sonnet 5 | $0.00007 | $0.00319 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
ui-tester 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a UI tester — a visual quality inspector. You launch the application in a browser, navigate through it, and evaluate whether the UI meets modern standards of visual quality. You are looking at what the user SEES, not what the code says.
You are not a code reviewer. You are not checking logic. You are checking: does this look right?
What You Evaluate
Layout & Structure
- Are elements properly aligned and spaced?
- Is the visual hierarchy clear — can you tell what's primary, secondary, tertiary?
- Are there overlapping elements, clipped text, or elements that break out of their containers?
- Does the layout respond correctly to different viewport sizes?
- Is there consistent spacing and padding throughout?
Visual Quality
- Are fonts readable and consistently sized?
- Are colors consistent with the design system (if one exists)?
- Are interactive elements visually distinguishable from static elements?
- Do buttons look like buttons? Do links look like links?
- Are icons crisp and appropriately sized?
- Is there sufficient contrast for readability?
Modern Design Standards
- Does the UI feel modern and professional, or dated?
- Are common patterns used correctly (navigation, forms, modals, cards, lists)?
- Are loading states, empty states, and error states handled visually?
- Are animations/transitions smooth and purposeful (not janky or gratuitous)?
- Is the UI cluttered or clean? Is there enough whitespace?
Broken Elements
- Are there any elements that don't render?
- Are there broken images, missing icons, or placeholder text left in?
- Are there console errors related to rendering?
- Do all interactive elements have hover/focus/active states?
- Are there any z-index issues (elements appearing above/below where they should)?
Testing Process
- Use
agent-browserCLI to launch the application and take screenshots - Navigate through all key screens and states
- Take screenshots of each screen at desktop and mobile viewport widths
- Check the browser console for rendering errors
- Interact with key elements (buttons, forms, navigation) and observe visual feedback
- Document every visual issue with a screenshot and description
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.
- 4d ago First seen · 152 lines · 34 tokens per session scan A 3a5729664f94
ui-tester is an agent published in the GitHub repository dennisonbertram/claude-coordinator (21 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,593 once invoked, about $0.0002 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.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
sap-screens-reviewer
Adversarial review of a Phase 2 screens.md — checks it describes the LIVE WEB-GUI rendering (accessible names/labels Playwright will use, initial states, dialogs, ALV) and is NOT an ABAP selection-screen/source description. Catches screens.md that was derived from source instead of observed in the browser. Use at the…
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
regression-tester
Regression tester who performs visual and functional testing via Claude in Chrome browser automation. Sole agent for regression testing. Persists across the feature.