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 agentmods add rules/m3au/playwright-bdd-cursor-template/playwrightgit clone --depth 1 https://github.com/m3au/playwright-bdd-cursor-templateWhat 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 | $0.00000 | $0.00645 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
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 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Standards
Locator Selection
Prefer Semantic Locators
- A: prefer
getByRole()for elements with semantic roles (button, heading, link, textbox, etc.) - A: prefer
getByText()when selecting by visible text - A: prefer
getByLabel()for form inputs - A: prefer
getByPlaceholder()for inputs with placeholders - A: prefer
getByTestId()for elements withdata-testidattributes
When to Use locator()
- Use
locator()only when semantic locators are not available or insufficient - Use
locator()for complex CSS selectors (e.g.,[class*="plugmodal__category"]) - Use
locator()when you need to chain selectors (e.g.,parentLocator.locator('.child')) - Use
locator()for attribute-based selection when no semantic alternative exists (e.g.,[itemprop="name"])
See tests/e2e/poms/components/cookie-banner.ts for semantic locator examples, tests/e2e/poms/components/cable-selector-popup.ts for locator() usage with complex selectors.
Auto-Waiting
Playwright Auto-Waiting
- Playwright automatically waits for elements to be ready before interactions
click(),fill(),type()automatically wait for element to be attached, visible, stable, enabled, and receiving events- After clicking links, Playwright automatically waits for navigation to complete
When Explicit Waits Are Needed
- N: use
waitForLoadState('load')orwaitForLoadState('domcontentloaded')after clicking links - Playwright auto-waits for navigation - N: use
waitForTimeout()- useexpect()assertions instead - Use
waitFor()only for state transitions (e.g.,waitFor({ state: 'attached' })) when not usingexpect() - Use
expect().toBeVisible()for visibility checks - it has built-in waiting and better error reporting
See tests/e2e/poms/pages/product-detail-page.ts for correct navigation handling without redundant waits.
Assertions
- Prefer
expect()overwaitFor()for better test reporting - Use
expect().toBeVisible()instead ofwaitFor({ state: 'visible' }) - Use
expect().toBeHidden()instead ofwaitFor({ state: 'hidden' }) - Use
expect().toHaveText()for text verification expect()assertions automatically wait and provide better error messages
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 First seen · 59 lines · 0 tokens per session scan A 9c39fcd707e5
playwright is a cursor rule published in the GitHub repository m3au/playwright-bdd-cursor-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 645 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.