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/idavidov13/agentic-playwright/selectorsnpx skills add idavidov13/agentic-playwright --skill selectorsgit clone --depth 1 https://github.com/idavidov13/agentic-playwrightWhat 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.00136 | $0.02438 |
| Opus 5 | $0.00068 | $0.01219 |
| Sonnet 5 | $0.00027 | $0.00488 |
| Haiku 4.5 | $0.00014 | $0.00244 |
Grade A, and why
selectors 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 3d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Selector Strategy
Critical
- Selector priority order is mandatory:
getByRole>getByLabel>getByPlaceholder>getByText>getByTestId. Move to the next option only when the previous one is not feasible. - NEVER use XPath (
page.locator('//...')or'xpath=...'). - NEVER use CSS class or ID selectors as the primary strategy (
page.locator('.btn-primary'),page.locator('#submit')). Acceptable only as an absolute last resort after ruling out every semantic option. - Exploration with
playwright-cliis mandatory before writing any selectors. No guessing from wireframes, docs, or screenshots. Read theplaywright-cliskill for the commands. - If the app cannot be reached or auth fails, stop and notify the human — never ship placeholder locators with guessed names.
- String values inside
getByText(...)come fromenums/{area}/*(e.g.Messages.LOGIN_ERROR). Never hardcode repeated UI strings. See theenumsskill. - Every page object covering forms or CRUD must include feedback / validation message selectors — success, error, field validation, toast, loading, empty state as applicable. A page object without them is incomplete.
- Locators are
getaccessors returningLocator— this is a style/readability convention in the scaffold. Playwright'sLocatoris lazy, sogetand areadonlyfield set in the constructor behave identically at runtime.
Instructions
Phase 1: Open and authenticate
Never generate selectors from assumptions or documentation alone. Before writing any locators or page objects, explore the live application by running playwright-cli in the terminal (read the playwright-cli skill). Do not use IDE browser MCP, Cursor browser tools, or any substitute — orchestrator rule: No Substitute UI Exploration. If playwright-cli cannot run, stop and notify the human.
playwright-cli open <APP_URL>
playwright-cli snapshot
If the page fails to load or requires authentication:
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.
- 3d ago First seen · 168 lines · 136 tokens per session scan A 8f9811cf1a6d
selectors is a skill published in the GitHub repository idavidov13/agentic-playwright (139 stars, last pushed 6d ago), licensed MIT. It adds 136 tokens to every session and 2,438 once invoked, about $0.0007 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
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
ac-qa-e2e-review
Reviews spec implementation with E2E visual browser validation via Playwright. Triggers on keywords: e2e review, visual review, spec review, browser validation.
ac-qa-test-e2e
Executes E2E tests from definition files with Playwright browser automation. Triggers on keywords: test e2e, run e2e, execute e2e test, e2e test runner.
ac-qa-browser
Opens browser at URL for E2E testing via playwright-cli. Provides CLI commands for navigation, screenshots, and interaction. Triggers on keywords: browser, open browser, playwright browser, e2e browser.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
qa/e2e-playwright
Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧.