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 skills add spencerpauly/awesome-cursor-skills --skill visual-qa-testinggit clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skillsWrote 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/skills/spencerpauly/awesome-cursor-skills/visual-qa-testing)<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/visual-qa-testing"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/visual-qa-testing/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/skills/spencerpauly/awesome-cursor-skills/visual-qa-testing"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/visual-qa-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00044 | $0.00599 |
| Opus 5 | $0.00022 | $0.00300 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
visual-qa-testing 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 6d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual QA
Use this skill after making UI changes to visually verify the result, catch console errors, and audit network requests — all without leaving Cursor.
How It Works
Cursor has a built-in browser (cursor-ide-browser MCP) that can navigate to URLs, take screenshots, read console messages, inspect network requests, and interact with page elements. This skill uses those tools to do a quick visual QA pass.
Steps
-
Ensure the dev server is running — check if there's already a terminal running the dev server. If not, start one in the background:
npm run devWait for the server to be ready (watch for the "ready" or localhost URL in the output).
-
Navigate to the page — use
browser_navigateto open the relevant page:Tool: browser_navigate Arguments: { "url": "http://localhost:3000", "take_screenshot_afterwards": true }If the change is on a specific route, navigate directly to it (e.g.,
/settings,/dashboard). -
Take a screenshot — capture the current state:
Tool: browser_take_screenshot Arguments: { "fullPage": true }Review the screenshot for visual issues: layout breaks, missing content, wrong colors, misaligned elements.
-
Check console for errors — look for JavaScript errors or warnings:
Tool: browser_console_messagesReport any errors, especially
TypeError,ReferenceError, failed imports, or React hydration mismatches. -
Audit network requests — check for failed API calls or unexpected requests:
Tool: browser_network_requestsLook for: 4xx/5xx status codes, CORS errors, excessively large responses, unnecessary duplicate requests.
-
Interact if needed — if the change involves interactive elements (buttons, forms, modals), use
browser_click,browser_fill, orbrowser_hoverto test the interaction, then take another screenshot to verify. -
Report findings — summarize:
- Screenshot shows the UI looks correct (or what's wrong)
- Console is clean (or list errors found)
- Network requests are healthy (or list failures)
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.
- 6d ago First seen · 70 lines · 44 tokens per session scan A 6dcd478831ac
visual-qa-testing is a skill published in the GitHub repository spencerpauly/awesome-cursor-skills (765 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 44 tokens to every session and 599 once invoked, about $0.0002 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 skills, from other repositories
image-compare
Compare two image files on disk and report what changed, region by region. Trigger on "what changed between these two images", "diff these PNGs", "did this render drift", "compare screenshots/exports/renders".
review-screenshot
A standard workflow for taking screenshots to check a user interface, using a dedicated review process for different verification modes.
visual-regression-lab
Compare captures; stitch lazy/animated pages.
visual-qa-vision-agent
Equips the AI agent with visual QA capabilities using Playwright/Puppeteer and the agent's innate Vision capabilities to self-correct UI layout, CSS alignment, and visual regressions.
visual-regression
Catch unintended visual drift between prototype iterations with deterministic screenshot diffs. Use when iterating on a prototype, before review handoff, or before promoting an SPA prototype to a real build. Default engine is Playwright toHaveScreenshot with masking, threshold, and per-OS baselines. Includes Chromatic…
visual-qa
Use when verifying that a UI renders correctly. Covers visual regression testing, responsive checks across breakpoints, cross-browser verification, and screenshot-based review of an implementation against a design.