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 n-n-code/n-n-code-skills --skill setup-playwrightgit clone --depth 1 https://github.com/n-n-code/n-n-code-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/n-n-code/n-n-code-skills/setup-playwright)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/setup-playwright"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/setup-playwright/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/n-n-code/n-n-code-skills/setup-playwright"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/setup-playwright.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.00093 | $0.02437 |
| Opus 5.5 | $0.00037 | $0.00975 |
| Sonnet 5.5 | $0.00019 | $0.00487 |
| Haiku 4.5 | $0.00009 | $0.00244 |
Grade A, and why
setup-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 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Playwright
Build the smallest reliable repo-owned Playwright setup that fits the repository's language, package boundaries, test runner, developer-tool, and CI conventions.
This is a system skill: it leaves behind a repo-owned harness or an explicitly
requested Playwright developer-tool artifact. Day-to-day test authoring and
live browser investigation belong to playwright-testing.
Ownership Boundary
Use this skill when the main artifact is one or more of:
- Playwright dependencies or browser binaries
- runner config, package placement, or monorepo wiring
- app startup through
webServeror an ecosystem-native equivalent - browser, device, environment, retry, reporter, or artifact configuration
- reusable-auth setup and ignored state files
- a minimal smoke check that proves the harness works
- CI install, smoke, sharding, or report-merge plumbing
- an explicitly requested repo-owned
@playwright/clideveloper dependency or script - host-targeted Playwright Test Agent definitions for a compatible Node Playwright Test harness
Use playwright-testing when the harness works and the task is a spec, test
review, flake diagnosis, locator change, mock decision, visual check, or
standalone playwright-cli investigation. If an environment-dependent install,
startup, container, or CI failure has no established cause, start with
project-platform-diagnose and return here once the repair is known.
Choose The Existing Ecosystem
Follow the strongest repository signal:
- Node/TypeScript/JavaScript:
@playwright/testunless another runner is already intentional. - Python with pytest: the official Playwright Pytest plugin and pytest-native fixtures/config.
- .NET: the repo's MSTest, NUnit, xUnit, or xUnit v3 project and Playwright .NET integration.
- Java: the repo's JUnit or TestNG module with its Maven or Gradle build.
Do not create a Node sidecar in a Python, .NET, or Java repo merely because its examples are more familiar. Load references/ecosystem-patterns.md before editing a non-Node harness.
What ships with it
5 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 · 217 lines · 93 tokens per session scan A 6c69111b6352
setup-playwright is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 2,437 once invoked, about $0.0004 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-31.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
playwright-qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review…
browser-agent
Autonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.
website-change-verifier
Verify website changes across source, routes, rendering, metadata, discovery surfaces, and deployment state. Use when a user asks to check a new or edited page, confirm an exact replacement, validate a route, inspect responsive behavior, verify metadata or sitemap changes, compare localhost with production, or…
browser-task-and-automation-and-delegation
A required procedure for browser actions carried out through a separate browser specialist. Browser actions include opening pages, filling forms, taking snapshots, performance checks, automated tests, and data collection.
playwright-skill
Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error…