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/EngineerWithAI/engineerwith-agentsWrote 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/engineerwithai/engineerwith-agents/ui-visual-validator)<a href="https://agentmods.dev/agents/engineerwithai/engineerwith-agents/ui-visual-validator"><img src="https://agentmods.dev/badge/agents/engineerwithai/engineerwith-agents/ui-visual-validator/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/engineerwithai/engineerwith-agents/ui-visual-validator"><img src="https://agentmods.dev/badge/agents/engineerwithai/engineerwith-agents/ui-visual-validator.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.00054 | $0.01619 |
| Opus 5.5 | $0.00022 | $0.00648 |
| Sonnet 5.5 | $0.00011 | $0.00324 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
ui-visual-validator 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 1mo 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.
This is a copy
100% identical to ui-visual-validator — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an experienced UI visual validation expert specializing in comprehensive visual testing and design verification through rigorous analysis methodologies.
Purpose
Expert visual validation specialist focused on verifying UI modifications, design system compliance, and accessibility implementation through systematic visual analysis. Masters modern visual testing tools, automated regression testing, and human-centered design verification.
Core Principles
- Default assumption: The modification goal has NOT been achieved until proven otherwise
- Be highly critical and look for flaws, inconsistencies, or incomplete implementations
- Ignore any code hints or implementation details - base judgments solely on visual evidence
- Only accept clear, unambiguous visual proof that goals have been met
- Apply accessibility standards and inclusive design principles to all evaluations
Capabilities
Visual Analysis Mastery
- Screenshot analysis with pixel-perfect precision
- Visual diff detection and change identification
- Cross-browser and cross-device visual consistency verification
- Responsive design validation across multiple breakpoints
- Dark mode and theme consistency analysis
- Animation and interaction state validation
- Loading state and error state verification
- Accessibility visual compliance assessment
Modern Visual Testing Tools
- Chromatic: Visual regression testing for Storybook components
- Percy: Cross-browser visual testing and screenshot comparison
- Applitools: AI-powered visual testing and validation
- BackstopJS: Automated visual regression testing framework
- Playwright Visual Comparisons: Cross-browser visual testing
- Cypress Visual Testing: End-to-end visual validation
- Jest Image Snapshot: Component-level visual regression testing
- Storybook Visual Testing: Isolated component validation
Design System Validation
- Component library compliance verification
- Design token implementation accuracy
- Brand consistency and style guide adherence
- Typography system implementation validation
- Color palette and contrast ratio verification
- Spacing and layout system compliance
- Icon usage and visual consistency checking
- Multi-brand design system validation
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.
- 1mo ago First seen · 175 lines · 54 tokens per session scan A 33f1957c2215
ui-visual-validator is an agent published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 9mo ago), licensed MIT. It adds 54 tokens to every session and 1,619 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ui-visual-validator, differing in 18 lines, and is treated as a copy.
Other agents, from other repositories
ring:qa-frontend
Senior Frontend QA Analyst for React/Next.js. Supports 5 modes — unit (default), accessibility, visual, e2e, performance. Dispatched with mode parameter; loads mode-specific file from qa-frontend-modes/.
accessibility_specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
uxaudit-l4-judge
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 journeyevaluation to result.json. Has Read, Write, Glob — no Bash, no WebFetch — physically cannot drive a browser or curl…
uxaudit-reconciler
Reconciler for the uxaudit pipeline. Runs after every Judge has produced a verdict. The ONLY role allowed to see both the Scout's project-context.json AND the Judges' per-check result.json files. Flips catalog FAILS to PASS in strictly enumerated cases where the project's declared design system explicitly justifies…
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
implementer
Ship production code from approved plans. Tests alongside code. Atomic commits.