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 skills add punkadillo/figma-code-composer --skill playwright-progit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/punkadillo/figma-code-composer/playwright-pro)<a href="https://agentmods.dev/skills/punkadillo/figma-code-composer/playwright-pro"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/playwright-pro.svg" alt="Measured on agentmods" 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.00077 | $0.01251 |
| Opus 5 | $0.00039 | $0.00626 |
| Sonnet 5 | $0.00015 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade A, and why
playwright-pro 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 4d 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.
This is a copy
100% identical to playwright-pro — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Pro
Production-grade Playwright testing toolkit for AI coding agents.
Available Commands
When installed as a Claude Code plugin, these are available as /pw: commands:
| Command | What it does |
|---|---|
/pw:init |
Set up Playwright — detects framework, generates config, CI, first test |
/pw:generate <spec> |
Generate tests from user story, URL, or component |
/pw:review |
Review tests for anti-patterns and coverage gaps |
/pw:fix <test> |
Diagnose and fix failing or flaky tests |
/pw:migrate |
Migrate from Cypress or Selenium to Playwright |
/pw:coverage |
Analyze what's tested vs. what's missing |
/pw:testrail |
Sync with TestRail — read cases, push results |
/pw:browserstack |
Run on BrowserStack, pull cross-browser reports |
/pw:report |
Generate test report in your preferred format |
Quick Start Workflow
The recommended sequence for most projects:
1. /pw:init → scaffolds config, CI pipeline, and a first smoke test
2. /pw:generate → generates tests from your spec or URL
3. /pw:review → validates quality and flags anti-patterns ← always run after generate
4. /pw:fix <test> → diagnoses and repairs any failing/flaky tests ← run when CI turns red
Validation checkpoints:
- After
/pw:generate— always run/pw:reviewbefore committing; it catches locator anti-patterns and missing assertions automatically. - After
/pw:fix— re-run the full suite locally (npx playwright test) to confirm the fix doesn't introduce regressions. - After
/pw:migrate— run/pw:coverageto confirm parity with the old suite before decommissioning Cypress/Selenium tests.
Example: Generate → Review → Fix
# 1. Generate tests from a user story
/pw:generate "As a user I can log in with email and password"
# Generated: tests/auth/login.spec.ts
# → Playwright Pro creates the file using the auth template.
# 2. Review the generated tests
/pw:review tests/auth/login.spec.ts
# → Flags: one test used page.locator('input[type=password]') — suggests getByLabel('Password')
# → Fix applied automatically.
# 3. Run locally to confirm
npx playwright test tests/auth/login.spec.ts --headed
# 4. If a test is flaky in CI, diagnose it
/pw:fix tests/auth/login.spec.ts
# → Identifies missing web-first assertion; replaces waitForTimeout(2000) with expect(locator).toBeVisible()
What ships with it
60 files 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.
- reference/assertions.md 2.2 KB
- reference/common-pitfalls.md 3.1 KB
- reference/fixtures.md 3.1 KB
- reference/flaky-tests.md 1.5 KB
- reference/golden-rules.md 906 B
- reference/locators.md 2.1 KB
- templates/accessibility/color-contrast.md 5.5 KB
- templates/accessibility/keyboard-navigation.md 5.2 KB
- templates/accessibility/screen-reader.md 5.6 KB
- templates/api/auth-headers.md 4.7 KB
- templates/api/error-responses.md 5.4 KB
- templates/api/graphql.md 5.9 KB
- templates/api/rate-limiting.md 5.5 KB
- templates/api/rest-crud.md 5.0 KB
- templates/auth/login.md 4.6 KB
- templates/auth/logout.md 4.1 KB
- templates/auth/mfa.md 5.1 KB
- templates/auth/password-reset.md 5.7 KB
- templates/auth/rbac.md 4.7 KB
- templates/auth/remember-me.md 5.6 KB
- templates/auth/session-timeout.md 4.3 KB
- templates/auth/sso.md 4.5 KB
- templates/checkout/add-to-cart.md 4.1 KB
- templates/checkout/apply-coupon.md 5.0 KB
- templates/checkout/order-confirm.md 4.1 KB
- templates/checkout/order-history.md 4.6 KB
- templates/checkout/payment.md 5.4 KB
- templates/checkout/update-quantity.md 4.8 KB
- templates/crud/bulk-operations.md 5.2 KB
- templates/crud/create.md 4.7 KB
- templates/crud/delete.md 5.1 KB
- templates/crud/read.md 4.6 KB
- templates/crud/soft-delete.md 4.7 KB
- templates/crud/update.md 5.6 KB
- templates/dashboard/chart-rendering.md 4.9 KB
- templates/dashboard/data-loading.md 4.9 KB
- templates/dashboard/date-range-filter.md 5.5 KB
- templates/dashboard/export.md 5.7 KB
- templates/dashboard/realtime-updates.md 5.1 KB
- templates/forms/autosave.md 5.3 KB
- templates/forms/conditional-fields.md 5.6 KB
- templates/forms/file-upload.md 5.2 KB
- templates/forms/multi-step.md 5.5 KB
- templates/forms/single-step.md 4.8 KB
- templates/forms/validation.md 5.8 KB
- templates/notifications/in-app.md 4.8 KB
- templates/notifications/notification-center.md 4.7 KB
- templates/notifications/toast-messages.md 5.2 KB
- templates/onboarding/email-verification.md 5.0 KB
- templates/onboarding/first-time-setup.md 5.3 KB
- templates/onboarding/registration.md 5.7 KB
- templates/onboarding/welcome-tour.md 4.8 KB
- templates/README.md 4.8 KB
- templates/search/basic-search.md 4.4 KB
- templates/search/empty-state.md 4.5 KB
- templates/search/filters.md 5.1 KB
- templates/search/pagination.md 4.4 KB
- templates/search/sorting.md 5.1 KB
- templates/settings/account-delete.md 5.7 KB
- templates/settings/notification-prefs.md 5.2 KB
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.
- 4d ago First seen · 125 lines · 77 tokens per session scan A 93bafbd0c5c3
playwright-pro is a skill published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 19d ago), licensed MIT. It adds 77 tokens to every session and 1,251 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to playwright-pro, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
ui-first-builder
Creates production-ready UI immediately from any description. Generates complete pages, components, and realistic mock data in FIRST response. Uses Next.js 16 + Tailwind + shadcn/ui. Never asks questions - infers everything from context. Triggers: UI creation, page building, component generation, build interface…
component-design
Apply a coherent visual system, responsive behavior, interaction states, and accessibility to Kun components.
coss-ui
Set up or extend a Next.js web app with Coss/UI — the official Cal.com design system, built on Base UI + Tailwind CSS v4 and installed through the shadcn CLI via the namespaced @coss/ registry. Two modes: Init (shadcn init @coss/style on a new project) and Add (pull @coss/ui primitives, single @coss/ components, or…
animated-icons
Add a Motion-animated icon to a Next.js app from a shadcn registry instead of hand-animating an SVG. Two registries, picked from the project's icon set: heroicons-animated (316 icons, shadcn add @heroicons-animated/ ) and hugeicons-animated (165 icons, shadcn add @hugeicons-animated/ , which also installs a shared…