visual-qa-testing

visual-qa-testing is a skill for Claude Code, Codex from spencerpauly/awesome-cursor-skills. It costs 44 tokens per session (599 once invoked), scanned A, original, CC0-1.0.

A visual quality-checking procedure for web applications that uses a browser to inspect pages, screenshots, console errors, and network requests.

In plain words
What is it for?
Use it to check a local web page, review a full-page screenshot, inspect browser messages, and audit requests made by the page.
Why use it?
It helps catch layout problems, missing content, browser errors, and failed requests after user-interface changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to check a local web page, review a full-page screenshot, inspect browser messages, and audit requests made by the page.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spencerpauly/awesome-cursor-skills/visual-qa-testing
Install

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.

Any agent
npx skills add spencerpauly/awesome-cursor-skills --skill visual-qa-testing
Clone the repo
git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for visual-qa-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/visual-qa-testing/github.svg)](https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/visual-qa-testing)
Your own site
<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.

agentmods 80×15 button for visual-qa-testing

Your own site · 80×15
<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>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 599 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 12 Apr 2026
  • Snyk pass 12 Apr 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 6dcd478831ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

resources/visual-qa-testing/SKILL.md · 70 lines

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

  1. 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 dev
    

    Wait for the server to be ready (watch for the "ready" or localhost URL in the output).

  2. Navigate to the page — use browser_navigate to 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).

  3. 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.

  4. Check console for errors — look for JavaScript errors or warnings:

    Tool: browser_console_messages
    

    Report any errors, especially TypeError, ReferenceError, failed imports, or React hydration mismatches.

  5. Audit network requests — check for failed API calls or unexpected requests:

    Tool: browser_network_requests
    

    Look for: 4xx/5xx status codes, CORS errors, excessively large responses, unnecessary duplicate requests.

  6. Interact if needed — if the change involves interactive elements (buttons, forms, modals), use browser_click, browser_fill, or browser_hover to test the interaction, then take another screenshot to verify.

  7. 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)

Read the full file on GitHub · 70 lines

Changes

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.

  1. 6d ago First seen · 70 lines · 44 tokens per session scan A 6dcd478831ac

Subscribe to this mod's changes

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.