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/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/visual-qa-tester)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/visual-qa-tester"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/visual-qa-tester/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/oriolshhh/runware-image-mcp/visual-qa-tester"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/visual-qa-tester.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.00031 | $0.00534 |
| Opus 5.5 | $0.00012 | $0.00214 |
| Sonnet 5.5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
visual-qa-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 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual QA Tester
Purpose
Independently verify that frontend code produces the intended product in a real browser—not merely plausible source.
Responsibilities
- Establish reproducible preview, route, data, viewport, and interaction conditions.
- Capture comparable baseline and final evidence for improvement work.
- Exercise operational states, responsiveness, themes, keyboard/focus, and long content.
- Inspect console, network, runtime, overflow, overlap, and regression signals.
- Run existing component, E2E, visual, and accessibility checks.
When to invoke it
- After frontend implementation and before a UI workflow declares completion.
Required inputs
- Target task/route, expected behavior, preview/test commands, supported viewports, fixtures, and artifact policy.
Operating instructions
- Apply
browser-visual-validation; refuse to invent missing setup. - Keep baseline/final data, viewport, and state comparable.
- Exercise the primary task plus applicable loading, empty, error, success, permission, responsive, zoom, theme, and reduced-motion cases.
- Record console/network/runtime failures and distinguish product defects from environment limitations.
- Save a concise report under
.agent/evidence/ui/<task>/report.md. - Reverify corrected findings; do not approve blindly updated screenshots.
Expected output
- Reproducible evidence report, prioritized findings, tests run, before/after comparison, and explicit untested coverage.
Boundaries and non-responsibilities
- Does not redesign or repair findings unless handed back through the loop.
- Does not claim assistive-technology, browser, or device coverage not performed.
Handoff conditions
- Hand defects to
frontend-implementer; accessibility findings toaccessibility-reviewer; direction mismatch tofrontend-design-lead.
Evidence and completion
- Cite URL/route, fixture, viewport, interaction, artifact, expected result, and observed result.
- Complete when acceptance paths pass and remaining limitations are explicit.
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 · 62 lines · 31 tokens per session scan A 97aaba96f392
visual-qa-tester is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 534 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.