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 agentmods add skills/jpoutrin/product-forge/qa-screenshot-validationnpx skills add jpoutrin/product-forge --skill qa-screenshot-validationgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/qa-screenshot-validation)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/qa-screenshot-validation"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/qa-screenshot-validation.svg" alt="Measured on agentmods" 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.00037 | $0.01968 |
| Opus 5 | $0.00018 | $0.00984 |
| Sonnet 5 | $0.00007 | $0.00394 |
| Haiku 4.5 | $0.00004 | $0.00197 |
Grade A, and why
qa-screenshot-validation 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.
How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Screenshot Validation Skill
Validate captured screenshots for layout correctness and handle masked or clipped elements.
Validation Process
After capturing each screenshot, evaluate it for:
- Element visibility - Is the target element fully visible?
- Layout integrity - Does the layout appear correct?
- Clipping/masking - Are elements unexpectedly cut off?
- Overlapping - Are elements overlapping incorrectly?
- Rendering issues - Missing images, broken icons, etc.
Common Issues to Detect
Masked/Clipped Elements
| Issue | Indicators | Action |
|---|---|---|
| Horizontal clipping | Element cut off on right edge | Resize viewport wider |
| Vertical clipping | Element cut off at bottom | Scroll or resize taller |
| Overflow hidden | Content abruptly ends | Check parent container |
| Modal cutoff | Dialog extends beyond viewport | Resize to fit modal |
Layout Problems
| Issue | Indicators | Action |
|---|---|---|
| Overlapping elements | Text over images, buttons over content | Document as bug |
| Misaligned elements | Uneven spacing, broken grid | Document as bug |
| Missing elements | Expected element not visible | Verify selector, check visibility |
| Broken responsive | Desktop layout on mobile viewport | Document as bug |
Automatic Resize Logic
When an element appears clipped on desktop viewport:
IF element is clipped AND viewport is desktop (>1024px):
1. Try increasing viewport width by 200px
2. Retake screenshot
3. If still clipped, try 1920x1080 (full HD)
4. If still clipped, document as layout bug
Playwright Resize Commands
// Get current viewport
const viewport = page.viewportSize();
// Resize wider
await page.setViewportSize({
width: viewport.width + 200,
height: viewport.height
});
// Standard breakpoints
await page.setViewportSize({ width: 1920, height: 1080 }); // Full HD
await page.setViewportSize({ width: 1440, height: 900 }); // Laptop
await page.setViewportSize({ width: 1280, height: 720 }); // HD
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.
- 2d ago First seen · 305 lines · 37 tokens per session scan A c3ff41362c5f
qa-screenshot-validation is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 1,968 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…