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 parisgroup-ai/imersao-ia-setup --skill qa-mobilegit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/qa-mobile)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/qa-mobile"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/qa-mobile/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/parisgroup-ai/imersao-ia-setup/qa-mobile"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/qa-mobile.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.00067 | $0.01488 |
| Opus 5 | $0.00034 | $0.00744 |
| Sonnet 5 | $0.00013 | $0.00298 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
qa-mobile 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 11d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile QA Skill
Systematic responsive QA using browser automation.
Viewports
| Device | Width | Height |
|---|---|---|
| iPhone SE | 375 | 667 |
| iPhone 14 Pro Max | 430 | 932 |
| iPad Mini | 768 | 1024 |
| iPad Pro | 1024 | 1366 |
| Desktop | 1440 | 900 |
QA Checklist
For each viewport, check:
Layout
- No horizontal overflow (no horizontal scrollbar)
- Content doesn't overflow containers
- Text is readable (min 12px on mobile)
- Touch targets are at least 44x44px
- No overlapping elements
Navigation
- Mobile nav is functional (hamburger/tabs)
- Links are tappable
- Sticky headers don't cover content
Components
- Cards display correctly
- Modals/dialogs fit viewport
- Forms are usable (inputs not too small)
- Carousels/sliders work with touch
Design System
- Semantic tokens used (no hardcoded colors)
- Spacing is proportional to viewport
- Typography scales properly (sm/md/lg breakpoints)
Browser Tool Selection
Use Playwright MCP as the primary browser tool. Fall back to claude-in-chrome only if Playwright MCP is unavailable.
For visual tests (screenshots, visual comparison, pixel-level checks), always use Playwright MCP — it provides headless screenshots with consistent rendering, which is essential for reliable visual validation.
Chromium for Testing (REQUIRED)
Before starting browser interactions, ensure the new Chromium headless mode is active. This uses the real Chrome browser (not the legacy headless shell), providing more authentic rendering and behavior that matches what real users see.
-
Install Chromium for Testing (if not already installed):
mcp__plugin_playwright_playwright__browser_installThis ensures the Chromium for Testing binary is available.
-
The Playwright MCP uses
channel: 'chromium'by default when configured — this opts into the new headless mode which is the real Chrome browser running headless, more reliable for visual QA than the legacy headless shell.
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.
- 11d ago First seen · 161 lines · 67 tokens per session scan A f871946b5c0f
qa-mobile is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 29d ago), licensed MIT. It adds 67 tokens to every session and 1,488 once invoked, about $0.0003 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
browser-validator
Automatically validate implementations in real browsers after code is written or when user says "test this", "test what you built in the browser", "check it in a real browser", or "validate at the breakpoints". Uses Chrome DevTools MCP to test responsive breakpoints (320px, 768px, 1024px), check accessibility…
feature-acceptance
A browser-based acceptance testing process that compares an online implementation with a product requirements document and, when available, an HTML prototype. It records what is complete, partial, missing, or inconsistent, with screenshots and prioritized blockers.
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
e2e-testing
Playwright-based end-to-end testing workflow.
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…