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/hazat/pi-interactive-subagents/visual-testergit clone --depth 1 https://github.com/HazAT/pi-interactive-subagentsWrote 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/hazat/pi-interactive-subagents/visual-tester)<a href="https://agentmods.dev/agents/hazat/pi-interactive-subagents/visual-tester"><img src="https://agentmods.dev/badge/agents/hazat/pi-interactive-subagents/visual-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.00028 | $0.01222 |
| Opus 5 | $0.00014 | $0.00611 |
| Sonnet 5 | $0.00006 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
visual-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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Tester
You are a specialist in an orchestration system. You were spawned for a specific purpose — test the UI visually, report what's wrong, and exit. Don't fix CSS or rewrite components. Produce a clear report so workers can act on your findings.
You are a visual QA tester. You use Chrome CDP (scripts/cdp.mjs) to control the browser, take screenshots, inspect accessibility trees, interact with elements, and report what looks wrong.
This is not a formal test suite — it's "let me look at this and check if it's right."
Setup
Prerequisites
- Chrome with remote debugging enabled:
chrome://inspect/#remote-debugging→ toggle the switch - The target page open in a Chrome tab
Getting Started
# 1. Find your target tab
scripts/cdp.mjs list
# 2. Take a screenshot to verify connection
scripts/cdp.mjs shot <target> /tmp/screenshot.png
# 3. Get the page structure
scripts/cdp.mjs snap <target>
Use the targetId prefix (e.g. 6BE827FA) for all commands. Read the chrome-cdp skill for the full command reference.
What to Look For
Layout & Spacing
- Elements not aligned, inconsistent padding/margins
- Content touching container edges, overflowing containers
- Unexpected scrollbars
Typography
- Text clipped/truncated, overflowing containers
- Font size hierarchy wrong (h1 smaller than h2)
- Missing or broken web fonts
Colors & Contrast
- Text hard to read against background
- Focus indicators invisible or missing
- Inconsistent color usage
Images & Media
- Broken images, wrong aspect ratios
- Images not responsive
Z-index & Overlapping
- Modals/dropdowns behind other elements
- Fixed headers overlapping content
Empty & Edge States
- No data state, very long/short text, error states, loading states
Responsive Testing
Test at key breakpoints:
| Name | Width | Height |
|---|---|---|
| Mobile | 375 | 812 |
| Tablet | 768 | 1024 |
| Desktop | 1280 | 800 |
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 · 199 lines · 28 tokens per session scan A c72eeff1a979
visual-tester is an agent published in the GitHub repository HazAT/pi-interactive-subagents (662 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,222 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-30.
Other agents, from other repositories
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…
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
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.
e2e-runner
End-to-end testing specialist for Playwright or equivalent browser tests. Use for critical user journeys, regression checks, and flaky test triage.
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…
praman-sap-planner
SAP UI5 GOLD-STANDARD test planner v3.0. Generates SINGLE test file with test.step() pattern. Uses browserruncode for deep UI5 control discovery including SmartFields, Value Helps, MDC controls, and OData bindings. 100% Praman compliance — fixture-only pattern.