Playwright is a framework for automating and testing websites through one API that drives Chromium, Firefox, and WebKit. Developers use it for end-to-end tests, browser automation scripts, and AI-agent web interactions. The catalogue add-ons help coding and AI agents use Playwright for testing and browser automation.
Borrowing it
Nothing to install: this file belongs to microsoft/playwright. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/playwright/main/.claude/skills/playwright-release-notes/SKILL.mdgit clone --depth 1 https://github.com/microsoft/playwrightWrote 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/microsoft/playwright/playwright-release-notes)<a href="https://agentmods.dev/skills/microsoft/playwright/playwright-release-notes"><img src="https://agentmods.dev/badge/skills/microsoft/playwright/playwright-release-notes/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/microsoft/playwright/playwright-release-notes"><img src="https://agentmods.dev/badge/skills/microsoft/playwright/playwright-release-notes.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.00063 | $0.03770 |
| Opus 5.5 | $0.00025 | $0.01508 |
| Sonnet 5.5 | $0.00013 | $0.00754 |
| Haiku 4.5 | $0.00006 | $0.00377 |
Grade A, and why
playwright-release-notes scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
html=$(curl -sfL "$page") || { echo "MISSING PAGE $url"; continue; } How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release notes
In this skill, 1.xx is the release (for example 1.64).
Every release has a ## Version 1.xx section in four files in docs/src/:
| Language | Notes | Docs base URL | GitHub release in |
|---|---|---|---|
| Node.js | release-notes-js.md |
https://playwright.dev/docs/ |
microsoft/playwright |
| Python | release-notes-python.md |
https://playwright.dev/python/docs/ |
microsoft/playwright-python |
| Java | release-notes-java.md |
https://playwright.dev/java/docs/ |
microsoft/playwright-java |
| .NET | release-notes-csharp.md |
https://playwright.dev/dotnet/docs/ |
microsoft/playwright-dotnet |
Write the Node.js notes and the three translations in the same PR, so every language has its notes when it starts its release. The language repos then add only their own significant changes, and each one writes its GitHub release from its section (step 3).
1. Node.js notes
In docs/src/release-notes-js.md, add a ## Version 1.xx section above the previous version, and use previous versions as a guide:
- Highlights come first, each with an emoji heading and a short sample. Ask teammates for help with them.
- Then
### New APIswith####groups,### Breaking Changes ⚠️,### Announcementsand### Browser Versions. Print the browser versions withnode utils/print_versions.js. - Refer to APIs with docs link macros:
[`method: Page.frameLocator`],[`property: Page.webmcp`],[`event: Page.dialogClosed`],[`option: Tracing.start.ariaSnapshots`],[Locator]. Each language's docs show them with that language's names. - Link other docs pages with relative paths:
[test locks](./test-parallel.md#test-locks).
2. Python, Java and .NET translations
In each of release-notes-python.md, release-notes-java.md and release-notes-csharp.md, add a ## Version 1.xx section above the previous version. Translate it from the Node.js section. Compare the Version 1.63 sections of the files to see what past translations dropped and changed.
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.
- 3d ago First seen · 157 lines · 63 tokens per session scan A 59a4c78c4cc7
playwright-release-notes is a skill published in the GitHub repository microsoft/playwright (98,383 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 3,770 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-21.
Other skills, from other repositories
compatibility-testing
Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.
Browser Agent QA Testing
Teach agents to use AI browser agents for exploratory and smoke QA with step budgets, evidence-based assertions, guardrails, and Playwright conversion.
proxy-setup
Set up test-proxy-recorder for any Playwright project. Covers the proxy CLI (test-proxy-recorder --port --dir), package.json scripts for the three-service architecture (UI app → proxy → backend API), playwright.config.ts webServer block pointing to /control, per-test fixtures using playwrightProxy.before(page…
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
playwright-best-practices
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions…
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.