Borrowing it
Nothing to install: this file belongs to DIGI-UW/OpenELIS-Global-2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DIGI-UW/OpenELIS-Global-2/develop/.ai/skills/playwright/SKILL.mdgit clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2Wrote 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/skills/digi-uw/openelis-global-2/playwright)<a href="https://agentmods.dev/skills/digi-uw/openelis-global-2/playwright"><img src="https://agentmods.dev/badge/skills/digi-uw/openelis-global-2/playwright.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.00082 | $0.00810 |
| Opus 5 | $0.00041 | $0.00405 |
| Sonnet 5 | $0.00016 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
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 7d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Skill
Use this skill when:
- planning one or multiple Playwright flows for a feature or PR
- authoring new Playwright tests
- debugging failing Playwright tests
- auditing existing tests for flaky selectors or anti-patterns
Primary Entrypoints
/plan-record-playwright- plan scope and flow inventory for one or multiple tests, then orchestrate write, audit, run, and recording stages/write-playwright-test- author new tests from requirements and register them correctly in Playwright project allowlists/debug-playwright- failure diagnosis and remediation workflow/audit-playwright- quality and maintainability audit workflow
Lifecycle
For AI-assisted development, prefer this sequence:
/plan-record-playwright/write-playwright-test/audit-playwright/debug-playwright(only when failures persist)
Core Non-Negotiables
- Read component/page-object/helper source before changing selectors.
- For failures, inspect screenshot/trace/runtime DOM before changing code.
- Prefer
data-testid,getByRole, andgetByLabelover CSS fallback chains. - Avoid
.first()unless uniqueness is proven and documented. - Use
videoPause()for demo pacing and avoidpage.waitForTimeout()for waits. - Do not create new Cypress tests. Cypress is deprecated; all new E2E work must use Playwright.
- NEVER use
response.ok()as the test pass/fail signal. UsewaitForResponsefor sync, assert on visible UI. - NEVER use
{ force: true }on Carbon inputs. Click the<label>instead. - NEVER use
.catch(() => false)onisVisible()— it returns boolean directly. - ALWAYS include at least one
expect()assertion per test.
Execution Invariants
- Never use
npx playwright test(or rawplaywright test) to run tests. Always usenpm run pw:testand related scripts (pw:test:ui,pw:test:headed,pw:test:video,pw:test:harness,pw:test:core-demo,pw:test:harness-demo,pw:test:demoalias). - For
harness,harness-demo, andharness-demo-video, verify analyzer harness stack preflight before execution (see/restart-analyzer-harness). TEST_USERandTEST_PASSmust be set for all Playwright projects.- Utility exceptions are allowed:
npx playwright show-traceandnpx playwright install. - Canonical operational reference:
frontend/playwright/README.md.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- commands/audit-playwright.md 1.8 KB
- commands/debug-playwright.md 1.6 KB
- commands/plan-record-playwright.md 2.2 KB
- commands/write-playwright-test.md 2.5 KB
- reference/debug-workflow.md 1.3 KB
- reference/plan-record-workflow.md 2.0 KB
- reference/selector-policy.md 1.4 KB
- reference/write-workflow.md 1.8 KB
- scripts/validate-playwright-project.py 2.8 KB runs code
- templates/PlaywrightE2E.spec.ts.template 2.4 KB
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.
- 7d ago First seen · 85 lines · 82 tokens per session scan A e7ab5a47c8c8
playwright is a skill published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (251 stars, last pushed yesterday), licensed MPL-2.0. It adds 82 tokens to every session and 810 once invoked, about $0.0004 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 skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.