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 andregusman-raiz/a-gusman-claude --skill ag-referencia-playwrightgit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/andregusman-raiz/a-gusman-claude/ag-referencia-playwright)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-referencia-playwright"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-referencia-playwright/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/andregusman-raiz/a-gusman-claude/ag-referencia-playwright"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-referencia-playwright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 254 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 260 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 263 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 281 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.02381 |
| Opus 5 | $0.00022 | $0.01190 |
| Sonnet 5 | $0.00009 | $0.00476 |
| Haiku 4.5 | $0.00004 | $0.00238 |
Grade A, and why
ag-referencia-playwright 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Playwright Patterns (Canonical 2026)
Referencia oficial para uso de Playwright em testes E2E, QAT, e automacao
browser. Baseado em playwright.dev/docs/best-practices + observacoes de
producao em raiz-platform, profdigital, jusraiz.
Quando ativar
- Spec QAT, E2E, smoke test
- Debug de fluxo browser (Playwright MCP)
- Configuracao de
playwright.config.ts - Refactor de teste flaky
- Setup de novo projeto com testes
Decisoes canonicas (sem ambiguidade)
1. Browser channel: SEMPRE Chromium isolado
// ✅ Default — sem channel
test('flow', async ({ page }) => { ... })
// ❌ NAO usar salvo regression policy/codecs/enterprise
test.use({ channel: 'chrome' })
Razoes oficiais (playwright.dev):
- Chromium fica a frente do Chrome estavel — pega regressoes antes
- Reproducibilidade: nao depende do que esta instalado no Mac
- Setup mais simples, sem licencas de codecs
2. Modo: headless default, headed para debug
// playwright.config.ts — default
use: { headless: true }
// CLI debug ad-hoc
npx playwright test --headed --debug
3. Isolation: 1 contexto por teste
// ✅ Default Playwright — cada test ganha context novo
test('a', async ({ page }) => { ... }) // context isolado
test('b', async ({ page }) => { ... }) // outro context
// ✅ Multi-user no mesmo teste
test('admin + user', async ({ browser }) => {
const adminCtx = await browser.newContext()
const userCtx = await browser.newContext()
// ...
})
4. Persistent context: APENAS para QAT manual com login
// Usar SO em workflow exploratorio com login repetido
import { chromium } from 'playwright'
const ctx = await chromium.launchPersistentContext(
'~/.cache/playwright-claude/<projeto>',
{ channel: 'chromium', headless: true }
)
NUNCA usar persistent context em CI — perde isolation.
Web-first assertions (eliminar flakiness)
❌ Anti-pattern: waitForTimeout
await page.click('button')
await page.waitForTimeout(2000) // ❌ flaky, lento, nao-deterministico
const text = await page.textContent('.result')
expect(text).toBe('OK')
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 · 290 lines · 44 tokens per session scan A ab5e53db6607
ag-referencia-playwright is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 2,381 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
ui-test
Runs UI tests described in plain English by driving real Chrome via the Claude-in-Chrome extension. Covers end-to-end flows (clicks, forms, assertions), visual checks (screenshot + optional baseline diff), accessibility (axe-core), performance (Web Vitals + light Lighthouse-style metrics), and an interactive --debug…
audit-ui-e2e
Runs a beginner-mind end-to-end UI audit of any running app — local dev server, staging, production, or a specific URL. Drives Chrome through every interactive element on the target surface, collects structured findings (severity, category, where, symptom, impact, repro, triage), and hands the result off to…
capture-screens
Automatically navigates a web app using Playwright MCP and captures context-aware named screenshots at each product feature state. Names each file semantically based on context (e.g., checkout-payment-form-filled.png). Outputs a manifest.json mapping filenames to descriptions and a summary report. Use when documenting…
browse
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. 100ms per command. Use when you need to test a…
test-browser
Run browser tests on pages affected by current PR or branch.
verify
Drive the Vite desktop SPA to verify AppShell / Workbench sidebar changes.