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 testdino-hq/playwright-skill --skill pomgit clone --depth 1 https://github.com/testdino-hq/playwright-skillWrote 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/testdino-hq/playwright-skill/pom)<a href="https://agentmods.dev/skills/testdino-hq/playwright-skill/pom"><img src="https://agentmods.dev/badge/skills/testdino-hq/playwright-skill/pom/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/testdino-hq/playwright-skill/pom"><img src="https://agentmods.dev/badge/skills/testdino-hq/playwright-skill/pom.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.00035 | $0.00155 |
| Opus 5.5 | $0.00014 | $0.00062 |
| Sonnet 5.5 | $0.00007 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
playwright-pom 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.
This is a copy
100% identical to playwright-pom — 6 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.
What it actually says
Playwright Page Object Model
Structure your test code for maintainability — know when POM helps and when simpler patterns win.
2 guides covering Page Object Model implementation and the decision framework for choosing between POM, fixtures, and helpers.
Guide Index
| Topic | Guide |
|---|---|
| Page Object Model patterns | page-object-model.md |
| POM vs fixtures vs helpers | pom-vs-fixtures-vs-helpers.md |
What ships with it
2 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.
- 1mo ago First seen · 18 lines · 35 tokens per session scan A e1147d948841
playwright-pom is a skill published in the GitHub repository testdino-hq/playwright-skill (402 stars, last pushed 14d ago), licensed MIT. It adds 35 tokens to every session and 155 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to playwright-pom, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
browser-agent
Autonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.
browser-task-and-automation-and-delegation
A required procedure for browser actions carried out through a separate browser specialist. Browser actions include opening pages, filling forms, taking snapshots, performance checks, automated tests, and data collection.
integration
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.
testing-patterns
Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.
frontend-visual-qa
Verify rendered frontend evidence after implementation, including screenshot comparison, responsiveness, overflow, visible states, and scoped visual regression. Use available browser tooling only; exclude static lookup, routine code review, lint, builds, onboarding, and tool detection.
scenario-testing
This skill should be used when writing tests, validating features, or needing to verify code works. Triggers on "write tests", "add test coverage", "validate feature", "integration test", "end-to-end", "e2e test", "mock", "unit test". Enforces scenario-driven testing with real dependencies in .scratch/ directory.