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/rules/oriolshhh/runware-image-mcp/visual-qa-tester)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-qa-tester"><img src="https://agentmods.dev/badge/rules/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/rules/oriolshhh/runware-image-mcp/visual-qa-tester"><img src="https://agentmods.dev/badge/rules/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.00014 | $0.00586 |
| Opus 5.5 | $0.00006 | $0.00234 |
| Sonnet 5.5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: visual-qa-tester
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.
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 · 64 lines · 14 tokens per session scan A 37a230b590aa
visual-qa-tester is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 586 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-09-03.
Other cursor rules, from other repositories
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
web-pages-e2e-test-maintenance
Keep web pages end-to-end coverage current.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rule "cypress-e2e-testing-cursorrules-prompt-file" from XD3an/awesome-ai-coding-all-in-one, covering persona, auto-detect typescript usage, end-to-end ui testing focus, best practices and input/output expectations.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
playwright
A set of guidelines for Playwright, a tool that controls a web browser to test websites and web applications.