Borrowing it
Nothing to install: this file belongs to borbiuk/band-play. 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/borbiuk/band-play/master/.claude/skills/playwright/SKILL.mdgit clone --depth 1 https://github.com/borbiuk/band-playWrote 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/borbiuk/band-play/playwright)<a href="https://agentmods.dev/skills/borbiuk/band-play/playwright"><img src="https://agentmods.dev/badge/skills/borbiuk/band-play/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/borbiuk/band-play/playwright"><img src="https://agentmods.dev/badge/skills/borbiuk/band-play/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.00124 | $0.04442 |
| Opus 5.5 | $0.00050 | $0.01777 |
| Sonnet 5.5 | $0.00025 | $0.00888 |
| Haiku 4.5 | $0.00012 | $0.00444 |
Grade A, and why
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 yesterday.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright tests for Band Play
How to work on the test suite. What a good test looks like (rules, severities) is the standard in e2e-review/references/rules.md; follow it while writing. Project conventions are in testing.md.
Check
package.jsonandplaywright.config.tsbefore relying on a script or project that this file does not list.
With an argument, run that project (unit, e2e, live) or spec file and report the result; without one, follow the request.
Projects and commands
| Project | What | Command |
|---|---|---|
unit |
Pure logic from src/ (@shared/* for src/shared, a relative ../../src/... import for content, background and downloads modules), no browser and no chrome global |
npm run test:unit |
dist |
Setup project (tests/setup/dist.setup.ts): runs npm run build and checks dist/manifest.json against package.json; no tests of its own |
runs by itself before e2e and live (a dependency) |
e2e |
The built extension (dist/) in Playwright's bundled Chromium, headless; Bandcamp pages come from snapshots, no network |
npm run test:e2e |
live |
Smoke checks against real bandcamp.com; defined only when BAND_PLAY_LIVE is set; never part of npm test |
npm run test:live (BAND_PLAY_LIVE=1 playwright test --project=live) |
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.
- yesterday First seen · 118 lines · 124 tokens per session scan A 7e7bf07c18fc
playwright is a skill published in the GitHub repository borbiuk/band-play (21 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 4,442 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-10-26.
Other skills, from other repositories
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
test-building-blocks
Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures. Read the relevant rule file before writing or modifying any test, handler, or fixture. Covers: deciding which kind of test to write, authoring a new test from…
extension-test
Set up and run unit, integration, and E2E tests for Chrome extensions. Covers Jest mocks for chrome. APIs and Puppeteer E2E with real Chrome.
testing-best-practices
Support QA and testing work across formats: planning checks, writing test cases, reviewing coverage, designing Playwright browser and component integration tests, creating locators, and keeping automated tests focused on observable product behavior.
e2e-tester
Test a web app like a QA person — open it in a real browser, click through flows, and report what's broken with screenshots and code references. Works on localhost. Use when the user wants to test their app, verify a flow works, check for visual bugs, or validate changes before pushing.
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…