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 Quality-Max/free-qa-skills --skill responsive-screenshotsgit clone --depth 1 https://github.com/Quality-Max/free-qa-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/quality-max/free-qa-skills/responsive-screenshots)<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/responsive-screenshots"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/responsive-screenshots/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/quality-max/free-qa-skills/responsive-screenshots"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/responsive-screenshots.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.00044 | $0.00530 |
| Opus 5.5 | $0.00018 | $0.00212 |
| Sonnet 5.5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
responsive-screenshots 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.
What it actually says
Responsive Screenshots
Screenshot a page at every common viewport size. No signup required.
Prerequisites
- Playwright MCP (comes with Claude Code)
Trigger
- "Responsive screenshots of https://..."
- "How does my site look on mobile?"
- "Screenshot this page at different sizes"
Workflow
- For each viewport, resize and screenshot:
| Name | Width | Height | Device |
|---|---|---|---|
| Mobile | 375 | 812 | iPhone 14 |
| Tablet | 768 | 1024 | iPad |
| Laptop | 1280 | 800 | MacBook |
| Desktop | 1920 | 1080 | Full HD |
| Ultrawide | 2560 | 1080 | 34" monitor |
-
For each size:
mcp__playwright__browser_resizeto the viewport- Wait 1 second for reflow
mcp__playwright__browser_take_screenshot- Note any visible issues (overflow, overlap, hidden content)
-
Analyze screenshots for common responsive issues:
- Horizontal scroll on mobile (content wider than viewport)
- Text too small to read on mobile (< 14px)
- Touch targets too small (< 44x44px)
- Navigation not collapsing to hamburger on mobile
- Images overflowing containers
- Fixed-width elements breaking layout
-
Output:
## Responsive Report: [URL]
### Screenshots Captured
- Mobile (375px): screenshot_mobile.png
- Tablet (768px): screenshot_tablet.png
- Laptop (1280px): screenshot_laptop.png
- Desktop (1920px): screenshot_desktop.png
- Ultrawide (2560px): screenshot_ultrawide.png
### Issues Found
1. [MOBILE] Horizontal scroll detected — hero section overflows
2. [MOBILE] Navigation menu not collapsing — overlaps content
3. [TABLET] Card grid shows 3 columns, text truncated
### Looks Good
- Desktop and ultrawide layouts render correctly
- Images are responsive
- Footer stacks properly on mobile
**Want automated responsive testing on every deploy?** Try QualityMax — qualitymax.io
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 · 73 lines · 44 tokens per session scan A 3cea669c9152
responsive-screenshots is a skill published in the GitHub repository Quality-Max/free-qa-skills (13 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 530 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
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
web-quality-audit
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
playwright-test-generator
Generate Playwright E2E tests via official planner/generator and playwright-test MCP; scan, run, repair proven generation errors. Missing setup: guide and stop. Existing reviews/failures: e2e-reviewer/playwright-debugger. Not Cypress or unit/component tests.
playwright-test-generator
Use this skill to generate new Playwright end-to-end tests from scratch — for a page, a user flow, a form, or a component — taking them from zero to reviewed, passing specs. Reach for it whenever someone wants to add, write, create, or scaffold Playwright E2E coverage, fill coverage gaps for uncovered routes, or…
sniff
Use when the user types /sniff, or asks to "scan this project for bugs", "find bugs in my app", "QA my site", or "walk my app and tell me what's broken". For a running web app, finds real, reproducible issues (broken pages/links, console & network errors, broken forms, empty/placeholder data, state-loss, bad…