playwright-rust: Skill for Claude Code

.claude/skills/driver-bump/SKILL.md

driver-bump is a skill for Claude Code from padamson/playwright-rust. It costs 87 tokens per session (1,686 once invoked), scanned A, original, Apache-2.0.

A maintenance workflow for updating the Playwright browser driver used by a Rust library. Playwright is a tool for controlling web browsers from code, and the workflow compares protocol and behaviour changes before changing the pinned version.

In plain words
What is it for?
Use it when updating the bundled driver, investigating a driver-bump issue, checking Rust and Python behaviour against each other, or validating trace fixtures and protocol changes.
Why use it?
A driver update can silently disable options or produce incorrect traces even when the test suite passes. Comparing several sources and running checks helps reveal those compatibility problems.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is padamson/playwright-rust's own configuration. It tells Claude Code how to work on playwright-rust itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything playwright-rust configures →

Reuse

Borrowing it

Nothing to install: this file belongs to padamson/playwright-rust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/padamson/playwright-rust/main/.claude/skills/driver-bump/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/padamson/playwright-rust

Made for: Claude Code.

Wrote 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.

agentmods badge for driver-bump

README.md
[![agentmods](https://agentmods.dev/badge/skills/padamson/playwright-rust/driver-bump/github.svg)](https://agentmods.dev/skills/padamson/playwright-rust/driver-bump)
Your own site
<a href="https://agentmods.dev/skills/padamson/playwright-rust/driver-bump"><img src="https://agentmods.dev/badge/skills/padamson/playwright-rust/driver-bump/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.

agentmods 80×15 button for driver-bump

Your own site · 80×15
<a href="https://agentmods.dev/skills/padamson/playwright-rust/driver-bump"><img src="https://agentmods.dev/badge/skills/padamson/playwright-rust/driver-bump.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,686 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.01686
Opus 5.5 $0.00035 $0.00674
Sonnet 5.5 $0.00017 $0.00337
Haiku 4.5 $0.00009 $0.00169

Measured 7d ago against content hash fa1ce4956eab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

driver-bump 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 7d 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.

.claude/skills/driver-bump/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Driver bump

The crate pins one Playwright driver (PLAYWRIGHT_VERSION in crates/playwright/build.rs) and speaks its JSON-RPC protocol. A bump is small in the diff and large in what it can break, because the driver drops parameters it does not recognize instead of rejecting them. A renamed parameter therefore turns a feature off with the whole suite green. Past releases have done exactly that:

  • 1.58 removed the devtools launch option, which then did nothing.
  • 1.63 renamed every tracingStart capture parameter, and traces came out empty.
  • 1.64 took a request's id verbatim as the trace call id, which turned the crate's integer ids into Unknown trace actions, and moved the trace format to v10. Neither was in the release notes.

So the job is to establish the delta first, then move the version.

1. Establish the delta

Compare the old and new tags across four sources. Each catches something the others miss.

  1. The protocol spec. Move PLAYWRIGHT_VERSION, run cargo xtask sync-protocol-spec, and read git diff protocol-spec with context, so events, initializers and internal: true markers count as well as added and removed lines. If only DRIVER_VERSION changes, the wire contract did not move. The sync needs no driver download.
  2. The public API. docs/src/api/*.md in the Playwright monorepo (since: vX.Y entries) and types/types.d.ts in the published playwright-core.
  3. The implementation. packages/playwright-core/src/client and src/server, for behavior the spec does not show: the dispatcher, the trace recorder, Chromium switches, selector engines.
  4. playwright-python. Its roll commit and the fixes around it on the matching release-X.Y branch (and main for a minor). Its new tests are the behavior spec for ours. It also pins the Node version the driver expects; match it.

For a patch release, gh api repos/microsoft/playwright/compare/vA...vB lists the cherry-picks and files in one call, and is usually the whole delta. Check whether packages/playwright-core/browsers.json is in the file list: if not, the browser builds are unchanged.

Read the full file on GitHub · 128 lines

Changes

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.

  1. 7d ago Changed · +3 lines fa1ce4956eab
  2. 9d ago First seen · 125 lines · 87 tokens per session scan A 619bc583f6ce

Subscribe to this mod's changes

driver-bump is a skill published in the GitHub repository padamson/playwright-rust (163 stars, last pushed 2d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,686 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-10-19.

Related

Other skills, from other repositories

compiler

Use when converting a refined markdown E2E test case into a standard Playwright .spec.ts file. Triggers on "compile this test", "convert to playwright", or "generate spec from markdown". Requires a stable markdown test case and a running dev server.

Autodesk/claude-browser-test-skills · 55 tokens

migration-validator

Safety verification checklist for C-to-Rust migrations. Validates compilation, unsafe block minimization, memory safety, API compatibility, and idiomatic Rust patterns. Use when: validate migration, check Rust safety, verify converted code, migration QA.

JuanMarchetto/agent-skills · 51 tokens

moli-webfetch

Fetch, inspect, crawl, and capture live, JavaScript-rendered websites with Moli. Use when Codex needs current web content, web research, fact lookup, link following, a bounded crawl, client-rendered or response-gated content, network diagnostics, or a standalone HTML, Markdown, JSON, semantic-tree, viewport or…

lexmount/moli · 90 tokens

moli-websearch

Search the web by keyword or reverse-search images with Moli to find subjects, sources, exact matches, or similar images—even when Moli is not named. For fetching a known URL, use moli-webfetch.

lexmount/moli · 49 tokens

moli-cdp-server

Start Moli's CDP server and connect Playwright, Puppeteer, or raw CDP clients. Use to run a headless-browser CDP endpoint, replace a Chromium process, attach over CDP, enable real layout and screenshot surfaces, or diagnose CDP discovery, connection, and target startup—even when Moli is not named.

lexmount/moli · 74 tokens

actionbook-web-test

Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…

actionbook/actionbook · 71 tokens