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 skills/jpeetz/agent-skills/playwright-e2e-testingnpx skills add JPeetz/agent-skills --skill playwright-e2e-testinggit clone --depth 1 https://github.com/JPeetz/agent-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/skills/jpeetz/agent-skills/playwright-e2e-testing)<a href="https://agentmods.dev/skills/jpeetz/agent-skills/playwright-e2e-testing"><img src="https://agentmods.dev/badge/skills/jpeetz/agent-skills/playwright-e2e-testing.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 | $0.00316 | $0.05910 |
| Opus 5 | $0.00158 | $0.02955 |
| Sonnet 5 | $0.00063 | $0.01182 |
| Haiku 4.5 | $0.00032 | $0.00591 |
Grade A, and why
playwright-e2e-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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
9 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.
- CHANGELOG.md 2.2 KB
- evals/eval_cases.json 4.8 KB
- LICENSE 1.0 KB
- references/ci-cd-patterns.md 2.5 KB
- references/locator-strategies.md 3.0 KB
- references/testing-types-matrix.md 3.2 KB
- scripts/flake-detector.sh 2.0 KB runs code
- scripts/generate-auth-profile.ts 3.4 KB runs code
- scripts/validate-playwright-setup.sh 2.2 KB runs code
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.
- 3d ago First seen · 800 lines · 316 tokens per session scan A 517e29081489
playwright-e2e-testing is a skill published in the GitHub repository JPeetz/agent-skills (5 stars, last pushed 10d ago), with no licence file. It adds 316 tokens to every session and 5,910 once invoked, about $0.0016 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-31.
Other skills, from other repositories
test-e2e-playwright
Activate when creating, generating, or debugging Playwright end-to-end (E2E) browser automation tests for web applications — trigger phrasings include "write a Playwright test for this user flow", "create an E2E login test", "debug failed Playwright test", "setup automated browser testing", "test form submission with…
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
test-review
Ревью только что написанных или изменённых автотестов на соответствие best practices TypeScript + Playwright (по официальной документации) и конвенциям вашего проекта. Используй по /test-review либо после написания/правки любого теста (UI E2E, API, UI+API, моки, visual, mobile) или Page Object/фикстуры/констант — до…
e2e-setup
Set up Playwright e2e automation tailored to this team and app. Probes the running app (auth mechanism, API surface, spec availability), interviews with recommendations instead of open questions, scaffolds the playwright/ folder, and records every decision in playwright/AUTOMATION.md for the other e2e skills to read.…
verify-fix
Re-test a bug fix after a developer resolves it. Pulls the original bug from Jira, re-executes the repro steps in the browser, checks for regressions, and updates the bug status. The final step in the SDT workflow before a ticket moves to Done. Use when: "verify fix", "retest", "is this fixed?", "check BUG-123"…
e2e-pom
Build and maintain Page Object Models by live element discovery — never by guessing selectors. Build mode pairs with the user: derives the element inventory from test cases, proves every locator against the running app, and confirms with highlighted screenshots before anything enters the POM. Heal mode runs…