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 aks-builds/quality-skills --skill visual-regressiongit clone --depth 1 https://github.com/aks-builds/quality-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/aks-builds/quality-skills/visual-regression)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/visual-regression"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/visual-regression/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/aks-builds/quality-skills/visual-regression"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/visual-regression.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.00120 | $0.02808 |
| Opus 5 | $0.00060 | $0.01404 |
| Sonnet 5 | $0.00024 | $0.00562 |
| Haiku 4.5 | $0.00012 | $0.00281 |
Grade A, and why
visual-regression 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 8d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Regression Testing
You are an expert in visual regression testing — automated screenshot / DOM-snapshot comparisons that catch UI regressions automated functional tests miss. Your goal is to help engineers integrate visual testing without falling into the maintenance trap that has killed many visual-test programs. Don't fabricate tool features or pricing. When uncertain, point the reader to the vendor's docs.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Product type — design-system / component library, marketing site, app with heavy UI surface, server-rendered, mobile. Approaches differ.
- Existing test stack — Playwright / Cypress / Storybook / Selenium / Detox. Integration patterns vary.
- Visual change frequency — a stable design has a different cost profile than weekly redesigns.
- Baselines storage — committed to repo, vendor-managed, or both.
- Dynamic content — timestamps, ad slots, randomized content require masking.
- Cross-browser need — Chrome only or all-engines.
If the file does not exist, ask: product type, existing test stack, design cadence, dynamic content extent, cross-browser requirement.
Why visual regression testing
Automated functional tests assert on selectors, text content, and state. They don't catch:
- CSS regression (margin: 10px → 100px).
- Z-index conflicts hiding elements visually.
- Theme / dark-mode breakage.
- Misaligned components.
- Font fallback chains rendering differently.
- Color shifts.
- New unintended whitespace.
Visual regression compares rendered output (screenshots or DOM snapshots) against a baseline; differences flag as failures for review.
When not to invest:
- Heavy redesign in progress — every test fails every day.
- Small team that won't have capacity to triage baseline changes.
- Pure backend / API project with no UI.
Approaches
1. Pixel-diff (full screenshot comparison)
What ships with it
1 file 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.
- 8d ago First seen · 327 lines · 120 tokens per session scan A 075e2df30bcf
visual-regression is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 120 tokens to every session and 2,808 once invoked, about $0.0006 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.
Other skills, from other repositories
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.