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 playwright-testinggit 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/playwright-testing)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/playwright-testing"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/playwright-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/n-n-code/n-n-code-skills/playwright-testing"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/playwright-testing.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.00114 | $0.02224 |
| Opus 5.5 | $0.00046 | $0.00890 |
| Sonnet 5.5 | $0.00023 | $0.00445 |
| Haiku 4.5 | $0.00011 | $0.00222 |
Grade A, and why
playwright-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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Testing
Turn a focused browser question or named product claim into the smallest durable evidence. Preserve the repository's runner and language; do not translate every Playwright task into Node Playwright Test.
Choose The Lane
Route by the artifact and state model, not by the word “Playwright.”
Live investigation
Use playwright-cli when the user explicitly selects Playwright investigation
or when the investigation serves the Playwright test work owned by this skill.
Inspect the running app, reproduce behavior, or collect evidence. This lane
does not require a repo-owned test harness and does not authorize adding
one. Keep the CLI agent-side unless the user asks for repo changes.
Generic ad hoc Chrome investigation and browser use default to
chrome-devtools-axi. Preserve an explicitly chosen browser/tool and its
session. AXI findings may feed a durable Playwright test; this skill owns that
test artifact and the existing runner's behavior.
Load references/playwright-cli-investigation.md.
Use the executable's help and official Playwright documentation for current command mechanics. This package supplies the investigation and test workflow; no separately installed skill is required. Verify runtime help when a local example or documentation page describes a different version.
Existing-harness test work
Use this lane when a working Playwright harness exists and the main artifact is a spec, test review, locator change, flake diagnosis, mock decision, or visual check. Inspect the active ecosystem before choosing syntax or commands.
Load references/ecosystem-testing.md for Python, .NET, or Java, or whenever runner semantics are uncertain.
For review-only requests, inspect the tests and report findings without editing specs, generating tests, or accepting new snapshots. Use only safe verification within scope; a baseline update cannot substitute for explaining a regression.
What ships with it
7 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 Changed · +6 lines · +16 tokens per session 76e9f38a6fcc
- 1mo ago Changed · +4 lines d5cc75e0b67f
- 1mo ago First seen · 182 lines · 98 tokens per session scan A de5dd4e1be0f
playwright-testing 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 114 tokens to every session and 2,224 once invoked, about $0.0005 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…