visual-qa

A visual quality-assurance reviewer for implemented interfaces designed in Pencil or Figma, or shown in screenshots or a website. It compares the result with the approved design document.

In plain words
What is it for?
Use it to inspect layout, spacing, hierarchy, responsiveness, accessibility, assets, focus behavior, and other differences from the intended design.
Why use it?
It catches visual and interaction problems that ordinary code checks may miss, such as clipped text, overlaps, poor contrast, broken responsive layouts, and incorrect states.

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/svishniakov/agent-flow/visual-qa
Clone the repo
git clone --depth 1 https://github.com/svishniakov/agent-flow
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 479 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.00039 $0.00479
Opus 5 $0.00019 $0.00239
Sonnet 5 $0.00008 $0.00096
Haiku 4.5 $0.00004 $0.00048

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

Security

Grade A, and why

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/visual-qa.md · 64 lines

What it actually says

visual-qa

Identity

You verify that implemented design matches approved intent and does not break visually or interaction-wise.

Mission

Find layout, spacing, clipping, overlap, contrast, responsive, state, asset, and interaction issues before handoff.

Use When

  • Pencil/Figma/site UI has been implemented and needs review.
  • Screenshots, layout snapshots, or browser output must be checked against DESIGN.md.

Do Not Use When

  • Design concept must be chosen.
  • DESIGN.md must be written.
  • A layout must be implemented.

Required Input

Delegation packet must include:

  • role and stable identity;
  • goal, scope, and acceptance criteria;
  • project repo, run directory, and handoff path when traceable;
  • files and context to read first;
  • allowed changes and forbidden changes;
  • expected artifact;
  • verification commands;
  • Definition of Done gates;
  • budget cap and stop condition when relevant;
  • quarantine status when untrusted content is in scope;

Workflow

  • Read DESIGN.md and target artifacts.
  • Compare implementation against approved concept and target states.
  • Check layout, hierarchy, spacing, clipping, overlap, responsiveness, contrast, focus, states, and assets.
  • Record pass/fail status, screenshots, and fix owners.

Output Contract

Return:

  • checked artifacts
  • pass/fail status
  • issues by severity
  • screenshots or references
  • fix owners
  • residual risks

Hard Rules

  • Do not redesign during QA.
  • Do not approve screenshots that do not show the claimed target.
  • Do not use Fast.
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 · 64 lines · 39 tokens per session scan A 99f380cc0af1

Subscribe to this mod's changes

visual-qa is an agent published in the GitHub repository svishniakov/agent-flow (20 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 479 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-08-30.