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/kubev2v/forklift-console-plugin/playwright-testinggit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWhat 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.00010 | $0.02155 |
| Opus 5 | $0.00005 | $0.01077 |
| Sonnet 5 | $0.00002 | $0.00431 |
| Haiku 4.5 | $0.00001 | $0.00215 |
Grade A, and why
playwright-testing 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Testing Workflow
Invoke with: "test the UI", "write an e2e test", "test in browser", "upstream test", "downstream test"
1. Upstream vs Downstream
This project has two tiers of E2E tests, both in this repo:
| Upstream | Downstream | |
|---|---|---|
| Location | testing/playwright/e2e/upstream/ |
testing/playwright/e2e/downstream/ |
| Tag | @upstream |
@downstream |
| Providers | Mocked via API intercepts | Real providers (vSphere, oVirt, OpenStack, OVA) |
| Credentials | Not required | Requires testing/.providers.json (not in repo) |
| Data | Static fixtures (fixtures/test-data.ts) |
Dynamic data from real provider inventory |
| Purpose | UI logic, rendering, form flows | Full integration -- closest to production |
| Run | npm run test:upstream (in testing/) |
npm run test:downstream (in testing/) |
Downstream tests are the priority -- they exercise real provider connections, actual migrations, and the full UI flow against a real cluster. Upstream tests are useful for fast feedback on UI-only changes.
Upstream is effectively a subset of downstream: upstream covers basic happy paths with mocked data, while downstream covers the same flows plus provider-specific behavior with real infrastructure.
2. Test Directory Structure
For a fuller “how to read this suite” guide (fixtures, intercepts, utils, lint layers), see testing/README.md.
testing/
playwright/
e2e/
upstream/ # Mocked tests (2 files)
downstream/ # Real provider tests (17+ files)
providers/
plans/
network-maps/
storage-maps/
fixtures/ # Test fixtures and helpers
intercepts/ # API mocking for upstream tests
page-objects/ # Page Object Model classes
utils/ # Utility functions (provider config, helpers)
types/ # TypeScript types
global.setup.ts # Authentication setup
global.teardown.ts # Resource cleanup
.providers.json.template # Provider credential template
e2e.env.template # Environment variable template
run-tests.sh # Containerized test runner (CI/Jenkins)
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.
- 2d ago First seen · 269 lines · 10 tokens per session scan A db9b18edd857
playwright-testing is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 2,155 once invoked, about $0.0001 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 cursor rules, from other repositories
webkit-browser
Cursor rule "webkit-browser" from duckduckgo/apple-browsers, covering webkit & browser development guidelines, webview configuration, basic webview setup, user scripts management and tab management.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
node-dependencies
Enforce Node.js versioning and package management best practices.
security-standards
Cursor rule "security-standards" from wjgogogo/cursor-rules, covering 安全规范, 核心原则 [p0], 输入验证, xss 防护 and csrf 防护.