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 rules/oriolshhh/runware-image-mcp/browser-visual-validationgit 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/browser-visual-validation)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/browser-visual-validation"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/browser-visual-validation.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.1 | $0.00017 | $0.00533 |
| Opus 5 | $0.00009 | $0.00267 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
browser-visual-validation 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 2d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: browser-visual-validation
Browser Visual Validation
Purpose
Replace code-only confidence with reproducible evidence from the rendered product.
When to use it
- After frontend changes and before completing UI review or improvement workflows.
Instructions
- Discover the repository's documented install and preview commands. Do not invent commands, silently change ports, or install browser tooling without approval.
- Establish a reproducible URL, route, fixture/account, viewport set, and target states. Record authentication or data limitations without exposing secrets.
- Capture a baseline before changes when improving existing UI.
- Use the strongest available browser surface: existing project tests, Playwright, browser-control/MCP, Storybook, or another repository-approved tool.
- Exercise the primary task plus loading, empty, error, success, keyboard/focus, narrow/wide layouts, zoom, reduced motion, and long content as applicable.
- Inspect console errors, failed network requests, runtime exceptions, layout overflow, obscured controls, and focus loss.
- Capture comparable final evidence and run existing unit/component/E2E/visual and accessibility checks. Never update visual baselines merely to make tests pass.
- Write
.agent/evidence/ui/<task>/report.mdwith environment, steps, evidence paths, findings, fixes, remaining risks, and untested coverage. Store binary artifacts only when useful and follow repository policy for committing them.
Output format
A reproducible browser-evidence report with baseline/final comparison, tested viewports/states/interactions, console/network observations, tests, and limitations.
Anti-patterns
- Declaring visual success from source inspection alone.
- Testing only one desktop happy path or using different data for before/after.
- Hiding console errors, blindly accepting screenshot changes, or claiming screen-reader coverage not performed.
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.
- 2d ago First seen · 51 lines · 17 tokens per session scan A 3b1357aec822
browser-visual-validation is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 533 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-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.
xiigen-user-journey-testing
Validate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.