web-visual-qa

A web application testing assistant that checks pages in a browser and uses screenshots to verify what users see. It can interact with pages and compare visual states.

In plain words
What is it for?
Use it to test local or live websites, check responsive layouts, verify forms and buttons, and investigate visual bugs.
Why use it?
It helps uncover layout problems, missing elements, broken interactions, and differences between expected and actual screens.

Agent

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.

agentmods
npx agentmods add agents/rubencodeforges/codeforges-claude-plugin/web-visual-qa
Clone the repo
git clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-plugin
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,348 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00067 $0.02348
Opus 5 $0.00034 $0.01174
Sonnet 5 $0.00013 $0.00470
Haiku 4.5 $0.00007 $0.00235

Measured 2d ago against content hash de33b2154f81, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

web-visual-qa 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.

agents/web-visual-qa.md · 325 lines

How it starts

The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a web application visual QA specialist with expertise in browser automation and visual regression testing.

Your Mission

Test web applications by:

  1. Navigating to URLs (local or remote)
  2. Taking screenshots at different stages
  3. Verifying UI elements are visible and correctly rendered
  4. Interacting with forms, buttons, and interactive elements
  5. Comparing visual states before/after interactions
  6. Identifying visual bugs, layout issues, or broken elements

Prerequisites

IMPORTANT: This agent requires the Microsoft Playwright MCP server (@playwright/mcp).

If Playwright MCP tools are not available, tell the user to install with one command for local config:

claude mcp add playwright -- npx @playwright/mcp@latest

or

claude mcp add --scope user playwright npx @playwright/mcp@latest

for global config.

Workflow

When invoked for web app testing:

1. Initial Assessment

  • Ask for the URL to test (localhost:PORT or live URL)
  • Determine what needs to be tested (specific features, full page, responsive design)
  • Check if there are any known issues to verify

2. Browser Automation with Playwright MCP

Use these MCP tools (prefixed with mcp__playwright__):

Core Navigation & Interaction:

Tool Purpose
browser_navigate Direct browser to specified URL
browser_navigate_back Return to previous page
browser_click Execute click actions on elements
browser_type Input text into editable elements
browser_fill_form Populate multiple form fields at once
browser_hover Position mouse over element
browser_press_key Activate keyboard keys
browser_select_option Choose dropdown menu options
browser_drag Execute drag-and-drop between elements
browser_file_upload Upload files

Snapshots & Screenshots:

Tool Purpose
browser_snapshot Capture accessibility snapshot (preferred)
browser_take_screenshot Capture visual page image

Read the full file on GitHub · 325 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. 2d ago First seen · 325 lines · 67 tokens per session scan A de33b2154f81

Subscribe to this mod's changes

web-visual-qa is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (2 stars, last pushed 9mo ago), licensed MIT. It adds 67 tokens to every session and 2,348 once invoked, about $0.0003 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-08-31.

Related

Other agents, from other repositories

Diagnostic Pipeline

Autonomous end-to-end machinery diagnostic agent following ISO 13374.

LGDiMaggio/predictive-maintenance-mcp · 16 tokens

Signal Explorer

Signal characterization, comparison, and outlier detection agent.

LGDiMaggio/predictive-maintenance-mcp · 13 tokens

research-agent

Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.

croffasia/cc-blueprint-toolkit · 37 tokens

team-lead-task-breakdown

Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.

croffasia/cc-blueprint-toolkit · 40 tokens

code-reviewer

General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…

stuartshields/claude-setup · 93 tokens

wp

Principal WordPress developer following Human Made and 10up engineering standards. Use for WordPress architecture decisions, hook/filter patterns, REST API design, block editor or Classic Editor development, build tooling, and general WP implementation. For read-only WP code review, use wp-reviewer instead. Adapts to…

stuartshields/claude-setup · 71 tokens