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/burhankhatri/e2e-testing/e2e-playwrightnpx skills add burhankhatri/e2e-testing --skill e2e-playwrightgit clone --depth 1 https://github.com/burhankhatri/e2e-testingWrote 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/burhankhatri/e2e-testing/e2e-playwright)<a href="https://agentmods.dev/skills/burhankhatri/e2e-testing/e2e-playwright"><img src="https://agentmods.dev/badge/skills/burhankhatri/e2e-testing/e2e-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 | $0.00103 | $0.06086 |
| Opus 5 | $0.00051 | $0.03043 |
| Sonnet 5 | $0.00021 | $0.01217 |
| Haiku 4.5 | $0.00010 | $0.00609 |
Grade A, and why
e2e-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 4d 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
17 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.
- references/api-testing-deep-dive.md 7.6 KB
- references/authentication-deep-dive.md 16 KB
- references/ci-pipeline-deep-dive.md 12 KB
- references/clock-and-time-mocking-deep-dive.md 7.5 KB
- references/common-pitfalls.md 19 KB
- references/debugging-deep-dive.md 12 KB
- references/fixtures-deep-dive.md 25 KB
- references/flaky-tests-deep-dive.md 14 KB
- references/iframes-and-shadow-dom-deep-dive.md 8.5 KB
- references/locators-deep-dive.md 16 KB
- references/mocking-deep-dive.md 15 KB
- references/nextjs-deep-dive.md 18 KB
- references/page-object-model-deep-dive.md 8.8 KB
- references/screenshots-and-media-deep-dive.md 8.1 KB
- references/test-data-management-deep-dive.md 6.7 KB
- references/test-organization-deep-dive.md 7.8 KB
- references/visual-regression-deep-dive.md 9.9 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.
- 4d ago First seen · 650 lines · 103 tokens per session scan A 7cc3ed8bf737
e2e-playwright is a skill published in the GitHub repository burhankhatri/e2e-testing (15 stars, last pushed 1mo ago), with no licence file. It adds 103 tokens to every session and 6,086 once invoked, about $0.0005 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
code-reviewer
Acts as a Senior QA Lead to review Playwright-Java code, ensuring architectural integrity and test stability using static analysis and live MCP verification.
healing-agent
Expert in diagnosing Playwright failures. Uses the @playwright MCP to verify live DOM state.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
playwright-test-results
Query Playwright CI test results from the aggregated DuckDB database. Answers questions about flaky tests, failure rates, slow tests, and per-run/SHA/PR results without hunting through GitHub artifacts.
playwright-trace
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.