testing-playwright

A set of Playwright rules for running end-to-end browser tests in this repository. End-to-end tests check an application through the same flows a user follows.

In plain words
What is it for?
Use it when running or configuring the repository's Playwright tests, including its build, preview server, Convex service, and failure traces.
Why use it?
It records the correct test folder, server startup, local services, command, and failure artifacts so tests run consistently.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/fmaclen/svelte-vibe-code/testing-playwright
Clone the repo
git clone --depth 1 https://github.com/fmaclen/svelte-vibe-code

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 154 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00154
Opus 5 $0.00000 $0.00077
Sonnet 5 $0.00000 $0.00031
Haiku 4.5 $0.00000 $0.00015

Measured yesterday against content hash 3ccf21ffce8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing-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.

.cursor/rules/testing-playwright.mdc · 13 lines

What it actually says

Playwright Testing

  • Test dir: e2e/
  • Server: Playwright starts the app with npm run build && npm run preview per playwright.config.ts.
  • Base URL: http://localhost:4173 (see config).
  • Convex: Ensure npm run convex is running when executing tests locally.
  • Run tests: npm test (sets the Convex test env var automatically).
  • Artifacts: Traces retained on failure; outputs under test-results/.
Changes

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.

  1. yesterday First seen · 13 lines · 0 tokens per session scan A 3ccf21ffce8d

Subscribe to this mod's changes

testing-playwright is a cursor rule published in the GitHub repository fmaclen/svelte-vibe-code (3 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 154 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.