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 AmadeusITGroup/otter --skill playwright-e2e-testinggit clone --depth 1 https://github.com/AmadeusITGroup/otterWrote 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/amadeusitgroup/otter/playwright-e2e-testing)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/playwright-e2e-testing"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/playwright-e2e-testing/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/amadeusitgroup/otter/playwright-e2e-testing"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/playwright-e2e-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01569 |
| Opus 5.5 | $0.00033 | $0.00628 |
| Sonnet 5.5 | $0.00016 | $0.00314 |
| Haiku 4.5 | $0.00008 | $0.00157 |
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 1mo 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright E2E Testing
Standardized architecture and creation process for Playwright end-to-end tests. Enforces a three-layer separation (Actions / Checks / Scenarios), a mandatory 3-gate creation workflow, and consistent coding standards across all UI teams.
Tooling: Playwright CLI vs Playwright MCP
Use the right tool for each phase of the workflow:
| Phase | Tool | Why |
|---|---|---|
| Exploring the app (understanding UI, discovering selectors, navigating flows) | Playwright MCP | Designed for exploratory automation — headed mode, structured accessibility snapshots in context |
| Writing & running tests (authoring test code, debugging failures, CI) | Playwright CLI (@playwright/cli) |
Designed for coding agents in large codebases — lower token cost, headless, concise output |
Playwright MCP — for exploration
Use Playwright MCP tools when you need to:
- Navigate the application to understand its structure before writing tests
- Discover available roles, labels, and test IDs on a page
- Verify a user journey works interactively before codifying it
Playwright CLI — for test authoring
Use the CLI when you need to:
- Verify test behavior during development (
playwright-cli open <url> --headed) - Debug failing selectors by inspecting snapshots (
playwright-cli snapshot) - Prototype interactions before writing test code (
playwright-cli click <ref>,playwright-cli fill <ref> <text>) - Run tests in headless mode for validation
Architecture: Actions / Checks / Scenarios
All E2E test code follows a strict separation of concerns:
| Layer | Directory | Contains | Rules |
|---|---|---|---|
| Actions | actions/<journey>-actions.ts |
User interactions (clicks, types, navigations) | No assertions. No side effects beyond UI interaction. Reusable across scenarios. |
| Checks | checks/<journey>-checks.ts |
Assertions (visibility, text, state) | No interactions. Pure verification. Composable. |
| Scenarios | scenarios/<feature>/ |
Composers wiring actions + checks | Readable as Given-When-Then. One journey per scenario. |
What ships with it
3 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.
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.
- 1mo ago First seen · 152 lines · 82 tokens per session scan A 2f7c8cde9630
playwright-e2e-testing is a skill published in the GitHub repository AmadeusITGroup/otter (59 stars, last pushed today), licensed BSD-3-Clause. It adds 82 tokens to every session and 1,569 once invoked, about $0.0003 per session on Opus 5.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
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…
troubleshooting
Diagnose and resolve common issues including test failures, build errors, performance regressions, and development environment problems. Use this skill whenever the user reports something broken, failing, timing out, hanging, or producing unexpected results. Trigger on test failures (elementIsStable timeouts, flaky…
operate-ai-stack
Develop, test, and troubleshoot this generated AI or ML workload across its framework, model and embedding providers, retrieval stores, interfaces, training, serving, and observability layers. Use when changing prompts, tools, agents, RAG, MCP, inference, fine-tuning, evaluations, or provider integration.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.