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 ytvee-dev/webdev-agent-kit --skill frontend-visual-qagit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWrote 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/ytvee-dev/webdev-agent-kit/frontend-visual-qa)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/frontend-visual-qa"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-visual-qa/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/ytvee-dev/webdev-agent-kit/frontend-visual-qa"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-visual-qa.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.01722 |
| Opus 5.5 | $0.00021 | $0.00689 |
| Sonnet 5.5 | $0.00011 | $0.00344 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
frontend-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 1mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Visual QA
Purpose
Verify a rendered frontend implementation against a Design Implementation Spec, Design Direction Contract, and supplied visual references when the task needs browser-rendered visual evidence.
This skill is not a general style-inspection tool. It exists for screenshot comparison, responsive rendering, visual regression evidence, visible state verification, and bounded repair loops when the implementation task includes fixes.
When To Use
- After implementation when visual acceptance requires comparing the rendered page with supplied screenshots or visual references.
- When the user asks to run visual QA, capture desktop/mobile screenshots, or compare rendered output to a design reference.
- When the issue is visibly rendered: responsive layout, wrapping, overflow, clipping, occlusion, viewport fit, visible interaction states, or screenshot-backed visual regression.
- When console or runtime errors must be checked because they affect the rendered UI during visual QA.
- When a loop contract says to repair material visual deviations and rerun rendered evidence.
When Not To Use
- Documentation-only, skill-only, backend-only, or static code review tasks.
- Design intake before implementation. Use
design-screenshot-spec. - Live Figma inspection or Figma MCP workflows.
- Font-family, font-size, font-weight, line-height, color, spacing, CSS variable, or token checks when values can be read from source files, copied inspect values, or the Design Implementation Spec.
- Computed-style checks whose only purpose is to read typography or token values.
- Routine lint, typecheck, build, refactor, onboarding, stack detection, or MCP detection.
Required Context
- Read
AGENTS.md. - Read
common/rendered-visual-verification-policy.md. - Confirm the classified task is
visual-qaand specifically needs rendered visual evidence. - Read
common/approved-patterns.md. - Read
common/anti-patterns.md. - Read
common/mobile-responsive-rules.mdwhen responsive behavior is in scope. - Read
common/verification-loop-rules.mdandcommon/bounded-retry-rules.mdwhen visual repair is in scope. - Read
project/verification-profile.mdwhen present. - Read the
Design Implementation Spec, Design Direction Contract, visual references, changed files, and relevant routes or pages. - Read
references/visual-qa-checklist.md.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 146 lines · 53 tokens per session scan A a6fe28056960
frontend-visual-qa is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,722 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
playwright-qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review…
playwright-skill
Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error…
playwright-core
Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-migration
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.