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/willcoliveira/qualiow-playwright-skillsWrote 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/rules/willcoliveira/qualiow-playwright-skills/cursor-rules)<a href="https://agentmods.dev/rules/willcoliveira/qualiow-playwright-skills/cursor-rules"><img src="https://agentmods.dev/badge/rules/willcoliveira/qualiow-playwright-skills/cursor-rules.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.00000 | $0.00595 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
cursor-rules 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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright E2E Skills
Decision Tree
- Write a NEW test: Read test-planning → explore with playwright-cli → write using test-generation → review with test-review
{{#if HAS_PLAYWRIGHT_159}}- Debug a FAILING test: Follow test-debugging workflow → use
--debug=cli+ CLI trace analysis → classify root cause → fix or report bug{{/if}} {{#if NO_PLAYWRIGHT_159}}- Debug a FAILING test: Follow test-debugging workflow → classify root cause → fix or report bug{{/if}} - Test an API with no browser: api-testing-patterns (APIRequestContext, zod contracts, bounded polling, request budgets)
- Prove determinism: pass-rate-and-flake-analysis (N consecutive runs, the four outcomes, flake triage)
- Understand PATTERNS: playwright-patterns (waitForResponse, toPass, expect.poll), data-strategy, page-object-conventions
- Follow CONVENTIONS: project-conventions (MUST/SHOULD/WON'T rules)
Key Rules
MUST
- Use web-first assertions (
await expect(locator).toBeVisible()) - Use named timeout constants, not hardcoded numbers
- Wrap page object methods in
test.step() - Use POM pattern — locators as readonly class properties
- Use short inner timeouts inside
toPassblocks
WON'T
- Use XPath selectors
- Use
page.waitForTimeout()for synchronization - Use
{ force: true }on actions - Use
networkidleingoto()orwaitForLoadState() - Use deprecated APIs (
waitForNavigation) - Write custom retry/polling loops (use
toPass()orexpect.poll())
Selector Priority
getByRole()> 2.getByLabel()> 3.getByText()> 4.getByTestId()> 5. CSS selector
waitForResponse Pattern
// Setup listener BEFORE the action
const responsePromise = page.waitForResponse('**/api/data')
await page.getByRole('button', { name: 'Submit' }).click()
const response = await responsePromise
toPass Pattern
await expect(async () => {
await expect(page.getByTestId('result')).toBeVisible({ timeout: 1_000 })
}).toPass({ timeout: 30_000, intervals: [1_000, 2_000, 5_000] })
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.
- yesterday Changed · +2 lines 0f67bda01574
- 6d ago First seen · 50 lines · 0 tokens per session scan A 413bfe7c6cb6
cursor-rules is a cursor rule published in the GitHub repository willcoliveira/qualiow-playwright-skills (16 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 595 tokens. 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 cursor rules, from other repositories
test-case-to-playwright
Convert Katalon True Platform/TestOps manual test cases, test suites, or requirement-linked cases into Playwright TypeScript automation. Use when you need to fetch/read Katalon Platform test cases and implement Playwright scripts, create or adapt a Playwright framework, apply Page Object Model and fixtures, or…
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
cypress
Cypress: cy commands, selectors, fixtures, intercepts.
playwright-agents
Playwright test agent workflows for planning, generating, and healing tests.
playwright-e2e-testing
E2E testing with Playwright.
vibe-test
How to use the vibe-test MCP server for browser testing.