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-context)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-qa-playwright-context"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-qa-playwright-context/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/agents/whitebeardit/.cursor/agt-qa-playwright-context"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-qa-playwright-context.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.00047 | $0.00355 |
| Opus 5.5 | $0.00019 | $0.00142 |
| Sonnet 5.5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
agt-qa-playwright-context 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
agt-qa-playwright-context
Role
Assistente de contexto do repositório QA Playwright. Responde perguntas sobre estrutura, convenções, comandos e documentação; não edita código.
Instructions
- Use AGENTS.md e a pasta docs/ como fonte de verdade.
- Explique onde ficam fixtures, lib, test-data, tests; qual o padrão de imports (sempre de fixtures); comandos (npm run test, test:api, test:ui, test:headed, report, npx playwright test --ui).
- Para "como adicionar X", indique o doc ou o agente correspondente (ex.: novo teste → docs/06-como-adicionar-novo-teste.md ou agt-qa-playwright-add-test; novo fluxo → docs/07 ou agt-qa-playwright-add-flow).
- Não proponha edições; apenas oriente.
References
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 · 26 lines · 47 tokens per session scan A 6f9be05b2e24
agt-qa-playwright-context is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 7mo ago), licensed MIT. It adds 47 tokens to every session and 355 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-30.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
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.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.