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-cherry-pick/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-cherry-pick)<a href="https://agentmods.dev/skills/microsoft/playwright/playwright-cherry-pick"><img src="https://agentmods.dev/badge/skills/microsoft/playwright/playwright-cherry-pick/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-cherry-pick"><img src="https://agentmods.dev/badge/skills/microsoft/playwright/playwright-cherry-pick.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.00000 | $0.00222 |
| Opus 5.5 | $0.00000 | $0.00089 |
| Sonnet 5.5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
playwright-cherry-pick 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.
What it actually says
Cherry-pick into a release branch
/playwright-cherry-pick <version> <commit>
Check out release-<version>, creating it if needed, synced to microsoft/playwright
(git fetch upstream release-<version> and use FETCH_HEAD, not a remote-tracking name).
Cherry-pick the commit and retitle it cherry-pick(#<pr>): <original title>, where <pr> is the
number from the trailing (#<pr>) of the original subject, dropped from the title. Body stays empty.
Report the result and stop.
Never push. The user asks explicitly, then: git push upstream release-<version>.
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 · 18 lines · 0 tokens per session scan A 51224c46ed12
playwright-cherry-pick is a skill published in the GitHub repository microsoft/playwright (98,383 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 222 tokens. 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-12.
Other skills, from other repositories
tadado-release
A release checklist for the Tadado2 repository. It defines how to test, package, commit, push, tag, publish a GitHub Release, and synchronize the local skill files.
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.
release-pr-quality-gate
Build an AgentWorks release or pull-request browser quality gate over saved suites and exact build identity. Use when a merge, deployment, or promotion needs an auditable QA decision.
dev-ship
Fechamento de feature — verificação goal-backward antes de declarar pronto. Roda Must-Haves do PLAN.md, executa o demo script, revisa o diff completo procurando bugs e restos (debug logs, TODOs, código morto), passa lente de segurança nos arquivos tocados, escreve SUMMARY.md e arquiva o plano. Use quando o usuário…
ikenga-contribute
Helps people contribute to Ikenga — draft a well-formed issue, run the full pull-request workflow (Conventional Commits + Changesets + tests), or onboard as a package author. It reads the project's own conventions and templates and fills them; it never invents its own rules. TRIGGER when the user wants to: file a bug…
release-validation
The final "Green Light". Checks all test suites (Unit, Int, E2E) and third-party reports.