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/zebbern/claude-code-guide/playwrightnpx skills add zebbern/claude-code-guide --skill playwrightgit clone --depth 1 https://github.com/zebbern/claude-code-guideWhat 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.00087 | $0.02243 |
| Opus 5 | $0.00044 | $0.01122 |
| Sonnet 5 | $0.00017 | $0.00449 |
| Haiku 4.5 | $0.00009 | $0.00224 |
Grade A, and why
playwright-skill 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- playwright-skill — 89% identical, 183 lines differ
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Skill
Opinionated, production-tested Playwright guidance — every pattern includes when (and when not) to use it.
50+ reference guides covering the full Playwright surface: selectors, assertions, fixtures, page objects, network mocking, auth, visual regression, accessibility, API testing, CI/CD, debugging, and more — with TypeScript and JavaScript examples throughout.
Golden Rules
getByRole()over CSS/XPath — resilient to markup changes, mirrors how users see the page- Never
page.waitForTimeout()— useexpect(locator).toBeVisible()orpage.waitForURL() - Web-first assertions —
expect(locator)auto-retries;expect(await locator.textContent())does not - Isolate every test — no shared state, no execution-order dependencies
baseURLin config — zero hardcoded URLs in tests- Retries:
2in CI,0locally — surface flakiness where it matters - Traces:
'on-first-retry'— rich debugging artifacts without CI slowdown - Fixtures over globals — share state via
test.extend(), not module-level variables - One behavior per test — multiple related
expect()calls are fine - Mock external services only — never mock your own app; mock third-party APIs, payment gateways, email
Guide Index
Writing Tests
| What you're doing | Guide | Deep dive |
|---|---|---|
| Choosing selectors | locators.md | locator-strategy.md |
| Assertions & waiting | assertions-and-waiting.md | |
| Organizing test suites | test-organization.md | test-architecture.md |
| Playwright config | configuration.md | |
| Page objects | page-object-model.md | pom-vs-fixtures-vs-helpers.md |
| Fixtures & hooks | fixtures-and-hooks.md | |
| Test data | test-data-management.md | |
| Auth & login | authentication.md | auth-flows.md |
| API testing (REST/GraphQL) | api-testing.md | |
| Visual regression | visual-regression.md | |
| Accessibility | accessibility.md | |
| Mobile & responsive | mobile-and-responsive.md | |
| Component testing | component-testing.md | |
| Network mocking | network-mocking.md | when-to-mock.md |
| Forms & validation | forms-and-validation.md | |
| File uploads/downloads | file-operations.md | file-upload-download.md |
| Error & edge cases | error-and-edge-cases.md | |
| CRUD flows | crud-testing.md | |
| Drag and drop | drag-and-drop.md | |
| Search & filter UI | search-and-filter.md |
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.
- ci/ci-github-actions.md 17 KB
- ci/ci-gitlab.md 12 KB
- ci/ci-other.md 16 KB
- ci/docker-and-containers.md 14 KB
- ci/global-setup-teardown.md 18 KB
- ci/parallel-and-sharding.md 16 KB
- ci/projects-and-dependencies.md 19 KB
- ci/reporting-and-artifacts.md 17 KB
- ci/SKILL.md 2.7 KB
- ci/test-coverage.md 15 KB
- core/accessibility.md 53 KB
- core/angular.md 41 KB
- core/api-testing.md 51 KB
- core/assertions-and-waiting.md 27 KB
- core/auth-flows.md 32 KB
- core/authentication.md 49 KB
- core/browser-apis.md 24 KB
- core/browser-extensions.md 15 KB
- core/canvas-and-webgl.md 20 KB
- core/clock-and-time-mocking.md 19 KB
- core/common-pitfalls.md 44 KB
- core/component-testing.md 46 KB
- core/configuration.md 25 KB
- core/crud-testing.md 31 KB
- core/debugging.md 27 KB
- core/drag-and-drop.md 29 KB
- core/electron-testing.md 22 KB
- core/error-and-edge-cases.md 39 KB
- core/error-index.md 58 KB
- core/file-operations.md 26 KB
- core/file-upload-download.md 30 KB
- core/fixtures-and-hooks.md 33 KB
- core/flaky-tests.md 31 KB
- core/forms-and-validation.md 39 KB
- core/i18n-and-localization.md 24 KB
- core/iframes-and-shadow-dom.md 21 KB
- core/locator-strategy.md 20 KB
- core/locators.md 28 KB
- core/mobile-and-responsive.md 58 KB
- core/multi-context-and-popups.md 22 KB
- core/multi-user-and-collaboration.md 20 KB
- core/network-mocking.md 45 KB
- core/nextjs.md 36 KB
- core/performance-testing.md 23 KB
- core/react.md 39 KB
- core/search-and-filter.md 43 KB
- core/security-testing.md 25 KB
- core/service-workers-and-pwa.md 20 KB
- core/SKILL.md 7.6 KB
- core/test-architecture.md 25 KB
- core/test-data-management.md 36 KB
- core/test-organization.md 31 KB
- core/third-party-integrations.md 30 KB
- core/visual-regression.md 35 KB
- core/vue.md 39 KB
- core/websockets-and-realtime.md 21 KB
- core/when-to-mock.md 28 KB
- LICENSE 1.0 KB
- migration/from-cypress.md 47 KB
- migration/from-selenium.md 45 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.
- 2d ago First seen · 138 lines · 87 tokens per session scan A 5617140a3cb1
playwright-skill is a skill published in the GitHub repository zebbern/claude-code-guide (4,596 stars, last pushed 4d ago), licensed MIT. It adds 87 tokens to every session and 2,243 once invoked, about $0.0004 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
cdb-scan
Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map…
mckinsey-consultant
McKinsey顾问式问题解决系统。从商业问题出发,通过假设驱动的结构化分析方法,生成McKinsey风格研究报告和PPT。融合Problem Solving方法论、MECE原则、Issue Tree拆解、Hypotheses形成、Dummy Page设计、智能数据收集和专业PPT生成能力。.
exam-coach
Quiz and coach the user for the Anthropic Claude certification exams using this repository's blueprints and official exam guides. Use when the user asks to practice, be quizzed, drill a domain, take a mock exam, or prepare for the Associate, Developer, or Architect certifications.
security-claude
Skill "security-claude" from rahozosman/security-claude, covering security architecture & threat modeling intelligence, how this skill is organized (progressive disclosure), 1. pick a mode, 2. core method (applies to every mode) and 3. doing a focused review.
bridger
Coordinate with another Claude Code session over the bridge — discover peers, ask them, answer their questions — INSTEAD of guessing or asking the user. Trigger this the moment the task depends on something another repo's session knows: a dependency/library that changed and this code consumes it, an API or schema…
run-tests
Run the pytest suite, report pass/fail counts and coverage, and identify untested code. Use when the user asks to run tests, check test coverage, or verify that changes didn't break anything.