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 agentmods add skills/musingfox/cc-plugins/playwrightnpx skills add musingfox/cc-plugins --skill playwrightgit clone --depth 1 https://github.com/musingfox/cc-pluginsWhat 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 | $0.00061 | $0.01821 |
| Opus 5 | $0.00030 | $0.00911 |
| Sonnet 5 | $0.00012 | $0.00364 |
| Haiku 4.5 | $0.00006 | $0.00182 |
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Test Writing
Overview
Write browser tests using @playwright/test, the official Playwright test runner. It provides auto-waiting, test isolation, built-in web assertions with auto-retry, and parallel execution out of the box.
Prefer @playwright/test for all testing scenarios. Use library mode (playwright) only for direct browser scripting needs: console error capture, network inspection, or custom automation outside a test context.
Project Setup
# Initialize Playwright in a project
npm init playwright@latest
# Or add to existing project
npm install -D @playwright/test
npx playwright install
Essential playwright.config.ts (for full multi-browser, reporter, and webServer config, see references/api-patterns.md):
import { defineConfig } from '@playwright/test';
export default defineConfig({
testDir: './tests',
fullyParallel: true,
retries: process.env.CI ? 2 : 0,
use: {
baseURL: 'http://localhost:3000',
trace: 'on-first-retry',
},
});
Test File Structure
Tests follow the pattern: tests/<feature>.spec.ts
import { test, expect } from '@playwright/test';
test.describe('Feature Name', () => {
test.beforeEach(async ({ page }) => {
await page.goto('/');
});
test('should perform expected behavior', async ({ page }) => {
// Arrange
const submitButton = page.getByRole('button', { name: 'Submit' });
// Act
await submitButton.click();
// Assert
await expect(page.getByText('Success')).toBeVisible();
});
});
Always use the AAA pattern: Arrange (locate elements), Act (interact), Assert (verify outcome).
Locator Strategy (Precision Order)
Apply locators in strict priority order — always prefer the highest-precision option available:
| Priority | Locator | When to Use | Stability |
|---|---|---|---|
| 1 | getByTestId('id') |
Element has data-testid attribute |
Highest — immune to text/structure changes |
| 2 | getByRole('role', { name }) |
Element has clear ARIA role and accessible name | Very high — maps from accessibility tree |
| 3 | getByLabel('label') |
Form inputs with associated <label> |
High — tied to label text |
| 4 | getByPlaceholder('text') |
Input with placeholder text | Medium-high — placeholder may change |
| 5 | getByText('text', { exact: true }) |
Visible text content | Medium — text may change |
| 6 | page.locator('[data-attr="val"]') |
Custom data attributes | Medium — depends on attribute stability |
| 7 | page.locator('css') |
Last resort — specific CSS selector | Low — fragile to DOM restructuring |
What ships with it
1 file 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.
- yesterday First seen · 253 lines · 61 tokens per session scan A 3ff2ca7db2f7
playwright is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 1,821 once invoked, about $0.0003 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…