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 seaworld008/Commonly-used-high-value-skills --skill playwright-progit clone --depth 1 https://github.com/seaworld008/Commonly-used-high-value-skillsWrote 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/seaworld008/commonly-used-high-value-skills/playwright-pro)<a href="https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/playwright-pro"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/playwright-pro/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/seaworld008/commonly-used-high-value-skills/playwright-pro"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/playwright-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 158 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 159 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 160 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 187 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 190 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00039 | $0.02131 |
| Opus 5.5 | $0.00016 | $0.00852 |
| Sonnet 5.5 | $0.00008 | $0.00426 |
| Haiku 4.5 | $0.00004 | $0.00213 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Pro
Use this skill to design, generate, review, debug, and stabilize production-grade Playwright test suites. It is the higher-discipline complement to a basic browser automation skill: focus on reliable assertions, maintainable fixtures, CI behavior, coverage strategy, and regression confidence.
When to Use
- Creating a new Playwright suite for a web app.
- Generating E2E tests from user stories, acceptance criteria, URLs, or existing manual QA steps.
- Fixing flaky Playwright tests in local runs or CI.
- Migrating Cypress, Selenium, Puppeteer, or manual smoke tests to Playwright.
- Adding regression tests for a bug fix.
- Reviewing test quality before merge.
- Testing authentication, checkout, forms, dashboards, uploads, permissions, onboarding, search, settings, or real-time flows.
- Adding visual, accessibility, API-assisted, or cross-browser checks.
- Integrating Playwright into GitHub Actions, CircleCI, Buildkite, Azure Pipelines, or other CI systems.
Skip When
- The task only needs quick page inspection or a one-off screenshot.
- Unit tests or integration tests would verify the behavior more cheaply and reliably.
- There is no runnable app or stable target environment and the user does not want setup work.
- The user explicitly asks to avoid browser automation.
Core Capabilities
- Bootstrap a maintainable Playwright configuration.
- Generate tests with resilient locators and web-first assertions.
- Design fixtures for auth, test data, API setup, and cleanup.
- Diagnose flakiness by timing, isolation, network, data, and selector stability.
- Review tests for anti-patterns and weak assertions.
- Migrate legacy suites while preserving behavior coverage.
- Integrate reports, traces, screenshots, and videos into CI.
- Build regression strategy around user-critical flows.
Recommended Workflow
1. Init: inspect framework, routes, auth, package manager, and test conventions.
2. Generate: write the smallest high-value tests for critical user paths.
3. Review: check locators, assertions, isolation, data setup, and failure diagnostics.
4. Run: execute locally in headless mode first, then headed for debugging if needed.
5. Stabilize: remove sleeps, isolate state, and add deterministic waits.
6. CI: shard, report, upload traces, and set retry policy.
7. Maintain: add regression tests for every escaped bug.
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 · 248 lines · 39 tokens per session scan A 9612c0614e15
playwright-pro is a skill published in the GitHub repository seaworld008/Commonly-used-high-value-skills (73 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,131 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
startup-qa-bot-getting-started
A guided first conversation for a product-checking assistant. It helps define a safe test environment and choose an initial check, such as following a sign-up flow or comparing two versions.
startup-qa-bot-ops
A working procedure for checking a product in a clearly separated test environment. It maintains a page map, records observations, compares known page lists, and reports reproducible problems.
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
startup-qa-bot-evidence
An offline comparison tool for two supplied page lists from the same test environment. It reports differences and status changes without opening a browser.
browser-qa-delivery
Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.