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 skills add AmariahAK/atlarix-skills --skill playwright-e2egit clone --depth 1 https://github.com/AmariahAK/atlarix-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/amariahak/atlarix-skills/playwright-e2e)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/playwright-e2e"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/playwright-e2e/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/playwright-e2e"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/playwright-e2e.svg" alt="Reviewed on agentmods" width="80" 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.00006 | $0.00357 |
| Opus 5 | $0.00003 | $0.00179 |
| Sonnet 5 | $0.00001 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 5d 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.
What it actually says
Playwright E2E Testing
When to use this skill
Use this skill when you need high-confidence coverage of user flows (auth, uploads, payments, chat flows) and you want stable, debuggable Playwright tests.
Core patterns
Test user behavior, not implementation
Prefer:
- interactions by role/label/text
- assertions on visible behavior
Avoid:
- brittle CSS selectors
- tests that depend on internal component structure
Deterministic test data
- seed DB or use fixtures
- avoid reliance on external APIs in CI (mock where needed)
Waits: rely on Playwright auto-waiting
Prefer:
await expect(locator).toBeVisible()
Avoid:
- arbitrary
sleepcalls
Debugging failures
- run headed locally when needed
- capture trace/video/screenshots in CI
- keep failure artifacts easy to access
Atlarix tool notes
- Build: add one e2e test per critical flow; keep them fast.
- Debug: reproduce the failing spec locally first; use trace viewer.
- Review: check selectors are resilient and assertions match user intent.
Common mistakes to avoid
- Using brittle selectors
- Global shared state between tests
- Flaky waits and timing-based sleeps
Mini-checklist
- Locators use roles/labels
- Data seeded deterministically
- Traces enabled in CI
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.
- 5d ago First seen · 57 lines · 6 tokens per session scan A 1faea6d33a2f
Playwright E2E Testing is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 6 tokens to every session and 357 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
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.
app-user-story-qa
End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
ui-aqa-flow
Workflow for automated QA: integration and end-to-end UI test automation, page objects, etc.
e2e-testing
Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is testing-web), NOT WCAG auditing (that is accessibility), NOT the…