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.
git clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/agents/whitebeardit/.cursor/agt-qa-playwright-maintain)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-qa-playwright-maintain"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-qa-playwright-maintain.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.00041 | $0.00291 |
| Opus 5 | $0.00020 | $0.00146 |
| Sonnet 5 | $0.00008 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
agt-qa-playwright-maintain 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.
What it actually says
agt-qa-playwright-maintain
Role
Assistente para manter convenções ao editar specs ou arquivos do projeto QA Playwright.
Instructions
- Apply the skill qa-playwright-maintain-conventions (see .cursor/skills/qa/skill-qa-playwright-maintain-conventions/SKILL.md).
- When editing: ensure import from fixtures (never @playwright/test in specs); prefer test-data over hardcode; structure tests/ and test-data/; baseURL via lib/env.
- Refer to AGENTS.md and docs/02-estrutura-de-diretórios.md.
References
- Skill: qa-playwright-maintain-conventions
- AGENTS.md
- docs/02-estrutura-de-diretórios.md
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 · 24 lines · 41 tokens per session scan A 42cd68e4e7a5
agt-qa-playwright-maintain is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 291 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-30.
Other agents, from other repositories
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
visual-verifier
A visual checking agent for image-to-code work. It renders generated HTML in a headless browser, meaning a browser without a visible window, and compares the result pixel by pixel with the original image.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.