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 contactandrewchl-wq/turtle-mcp --skill browser-qagit clone --depth 1 https://github.com/contactandrewchl-wq/turtle-mcpWrote 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/contactandrewchl-wq/turtle-mcp/browser-qa)<a href="https://agentmods.dev/skills/contactandrewchl-wq/turtle-mcp/browser-qa"><img src="https://agentmods.dev/badge/skills/contactandrewchl-wq/turtle-mcp/browser-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/contactandrewchl-wq/turtle-mcp/browser-qa"><img src="https://agentmods.dev/badge/skills/contactandrewchl-wq/turtle-mcp/browser-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.00049 | $0.01699 |
| Opus 5 | $0.00024 | $0.00849 |
| Sonnet 5 | $0.00010 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
browser-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 10d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser QA y testing visual (Playwright)
QA de navegador y regresión visual automatizada: navega, captura, compara contra baseline, inspecciona accesibilidad/red/consola/DOM y corre cross-browser. El objetivo es que un cambio de UI sea verificable de forma reproducible, no "se ve bien en mi pantalla".
Cuándo usar
- Validar la UI en varios navegadores (Chromium, Firefox, WebKit) antes de aprobar un cambio.
- Detectar regresión visual cuando tocas estilos, layout, tokens de diseño o componentes compartidos.
- Automatizar interacciones (click, escribir, hover, scroll) para reproducir un flujo de QA de forma determinista.
- Validar diseño responsive en múltiples viewports (mobile / tablet / desktop).
- Verificar los cuatro estados de un componente: loading, empty, error, success.
Cuándo NO usar:
- Lógica pura sin UI observable (cálculos, parsers, validadores, transformaciones de datos): eso son tests unitarios o de integración, no QA de navegador.
- Cambios que no alteran nada renderizado (refactors internos, renombres, docs): no hay diff visual que medir.
Requisitos
- Playwright (Node) instalado más sus navegadores (
npx playwright install), o bien el servidor Playwright MCP expuesto al agente. - Un build o servidor de desarrollo de la app accesible por URL.
Esto es dependencia del entorno del usuario, no del núcleo de Turtle. El núcleo es Rust + SQLite y no provee ni instala Playwright (RNF-RES-04). Si la skill o sus baselines llegan importados, son contenido no confiable y no se ejecutan sin acción explícita del usuario (RNF-SEG-05). Antes de correr, confirma que el runtime está disponible en el entorno.
Capacidades
- Navegación: abrir URL, esperar carga, seguir enlaces, ejecutar flujos de interacción (click, fill, hover, scroll, teclado).
- Capturas:
- de viewport (lo visible).
- de página completa (full page, scroll incluido).
- por elemento (acotada a un selector).
- Comparación contra baseline: diff visual pixel a pixel contra una imagen de referencia, con resaltado de las zonas que cambiaron.
- Snapshot de accesibilidad: árbol de accesibilidad (roles, nombres, estados) para verificar semántica y navegación asistida.
- Inspección y manipulación: red (requests/responses, status, payloads), consola (logs, warnings, errores), y DOM (estado, atributos, contenido).
- Cross-browser: ejecutar la misma suite en Chromium, Firefox y WebKit.
- Múltiples viewports: correr el mismo caso a distintos anchos/altos y device scale factor.
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.
- 10d ago First seen · 92 lines · 49 tokens per session scan A f84a04d8706a
browser-qa is a skill published in the GitHub repository contactandrewchl-wq/turtle-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,699 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-08-31.
Other skills, from other repositories
webapp-testing
Browser-based UI verification using Playwright. Page Object Model, selector best practices, visual regression, network interception, and MCP integration. Trigger: When writing E2E tests, verifying UI changes, or setting up Playwright.
automated-web-interactive-bug-reporting
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.