Borrowing it
Nothing to install: this file belongs to verdexhq/verdex-mcp. 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/verdexhq/verdex-mcp/main/.claude/skills/verdex-playwright-complete/SKILL.mdgit clone --depth 1 https://github.com/verdexhq/verdex-mcpWrote 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/verdexhq/verdex-mcp/verdex-playwright-complete)<a href="https://agentmods.dev/skills/verdexhq/verdex-mcp/verdex-playwright-complete"><img src="https://agentmods.dev/badge/skills/verdexhq/verdex-mcp/verdex-playwright-complete/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/verdexhq/verdex-mcp/verdex-playwright-complete"><img src="https://agentmods.dev/badge/skills/verdexhq/verdex-mcp/verdex-playwright-complete.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.00061 | $0.02720 |
| Opus 5 | $0.00030 | $0.01360 |
| Sonnet 5 | $0.00012 | $0.00544 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
verdex-playwright-complete 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 10d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verdex Playwright Complete Workflow
Complete test authoring in three phases: Explore → Select → Test
When to Use This Skill
Use this skill when you need to:
- Explore unfamiliar web applications and map user workflows
- Write stable, maintainable Playwright selectors that avoid positional
.nth()selectors - Create production-ready Playwright tests following best practices
- Understand complex UIs through progressive DOM exploration
The Complete Workflow
Phase 1: Explore & Map Workflows 🗺️
Goal: Understand the application and user journeys before writing any code
When to read the detailed guide: When starting work on a new application or feature
- Read guides/workflow-discovery.md for interactive exploration techniques
- Use Verdex MCP browser tools (
browser_navigate,browser_click,browser_snapshot) with refs - Document user journeys, state transitions, and assertion points
- Identify all interactive elements and their behaviors
Phase 2: Build Stable Selectors 🎯
Goal: Convert exploration discoveries into production-ready Playwright selectors
When to read the detailed guide: After workflow exploration, when you have refs and need selectors
- Read guides/selector-writing.md for comprehensive selector patterns
- Use the Container → Content → Role pattern
- Apply progressive DOM exploration (
resolve_container,inspect_pattern,extract_anchors) - Check uniqueness first—many elements need only simple selectors
Phase 3: Write Idiomatic Tests ✍️
Goal: Transform selectors and workflows into clean, maintainable Playwright tests
When to read the detailed guide: When you have selectors and workflows ready to code
- Read guides/playwright-patterns.md for test structure and patterns
- Follow Arrange-Act-Assert pattern
- Use Playwright's auto-waiting (avoid manual waits)
- Create independent, focused tests
What ships with it
3 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.
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.
- 10d ago First seen · 324 lines · 61 tokens per session scan A 5bb0cf320a80
verdex-playwright-complete is a skill published in the GitHub repository verdexhq/verdex-mcp (17 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 2,720 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-30.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…