agentmods.dev

add-playwright-test

add-playwright-test is a skill for Codex from alexhvastovich/playwright-ai-pom-starter. It costs 78 tokens per session (1,066 once invoked), scanned A, original, MIT.

A workflow for creating and maintaining Playwright UI tests, which automatically check how a website works in a browser. It covers planning a user flow, generating one scenario, validating it, and investigating reproducible failures.

In plain words
What is it for?
Use it to plan new browser flows, generate tests, update locators, or investigate failing UI tests. It uses page objects, which keep browser actions and selectors in organized classes.
Why use it?
It gives browser tests a consistent structure and review process, reducing the risk of generated tests that do not fit the repository or reliably check the intended behavior.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions subagents; mentions AGENTS.md; $skill-name invocation.

not rated 5repo 1mo ago A scan 78 tokens original MIT

Good fit Use it to plan new browser flows, generate tests, update locators, or investigate failing UI tests. It uses page objects, which keep browser actions and selectors in organized classes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alexhvastovich/playwright-ai-pom-starter/add-playwright-test
View source ↗ alexhvastovich/playwright-ai-pom-starter
Install

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.

Any agent
npx skills add alexhvastovich/playwright-ai-pom-starter --skill add-playwright-test
Clone the repo
git clone --depth 1 https://github.com/alexhvastovich/playwright-ai-pom-starter

Made for: Codex.

Wrote 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.

agentmods badge for add-playwright-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/alexhvastovich/playwright-ai-pom-starter/add-playwright-test/github.svg)](https://agentmods.dev/skills/alexhvastovich/playwright-ai-pom-starter/add-playwright-test)
Your own site
<a href="https://agentmods.dev/skills/alexhvastovich/playwright-ai-pom-starter/add-playwright-test"><img src="https://agentmods.dev/badge/skills/alexhvastovich/playwright-ai-pom-starter/add-playwright-test/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.

agentmods 80×15 button for add-playwright-test

Your own site · 80×15
<a href="https://agentmods.dev/skills/alexhvastovich/playwright-ai-pom-starter/add-playwright-test"><img src="https://agentmods.dev/badge/skills/alexhvastovich/playwright-ai-pom-starter/add-playwright-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,066 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.01066
Opus 5 $0.00039 $0.00533
Sonnet 5 $0.00016 $0.00213
Haiku 4.5 $0.00008 $0.00107

Measured 12d ago against content hash 9f771f828f8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

add-playwright-test 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 12d 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.

skills/add-playwright-test/SKILL.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add a Playwright test

Follow the repository architecture. Treat generated code as a draft until it passes the same checks as human-written code.

Select the agent

  • Use playwright_test_planner to explore a flow and save a plan in specs/.
  • Use playwright_test_generator to implement one scenario from that plan.
  • Use playwright_test_healer only after a reproducible test failure.

For a complete new flow, run planner, then generator, then the validation gate. Invoke healer only if the gate fails for test-code reasons.

Complete flow

  1. Read AGENTS.md and the relevant file in specs/.
  2. Ask playwright_test_planner to explore the flow through seeds/login.seed.spec.ts and save a precise Markdown plan.
  3. Review the plan for intent, independence, data safety, and expected results.
  4. Use $name-playwright-test to assign the scenario's stable test case ID, title, and file name.
  5. Ask playwright_test_generator to implement one named scenario from the plan while obeying the POM and locator contracts below.
  6. Move selectors and browser actions into a class in pages/.
  7. Add its lazy getter to pages/ManagePage.ts.
  8. Keep fixture wiring in fixtures/pom.fixture.ts.
  9. Keep the generated test behavior-focused and import from that fixture.
  10. Run the narrow test, then npm test.
  11. If a test fails, inspect the trace, screenshot, DOM, and product behavior.
  12. Invoke playwright_test_healer only when evidence identifies test code as the responsible layer. Re-run the narrow test and full gate afterward.

Test-id convention

  • Use data-testid as the product attribute and getByTestId() in Playwright.
  • Name IDs by stable meaning, not layout: btn-login, input-email, nav-user-menu, error-login.
  • Use lowercase kebab-case with an element-role prefix.
  • Do not encode styling, position, generated IDs, or changing copy.
  • Do not add a test ID when getByRole() or getByLabel() is already unique and stable.
  • Keep every locator in a Page Object. Tests never call page.locator().

Read the full file on GitHub · 105 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 12d ago First seen · 105 lines · 78 tokens per session scan A 9f771f828f8f

Subscribe to this mod's changes

add-playwright-test is a skill published in the GitHub repository alexhvastovich/playwright-ai-pom-starter (5 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,066 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-31.

Browser automationE2E testingTesting
Related

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).

garrytan/gstack · 32 tokens

playwright-cli

A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.

UnicomAI/wanwu · 76 tokens

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.

anthropics/skills · 35 tokens

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".

get-bb/bb · 57 tokens

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.

hashgraph-online/awesome-codex-plugins · 58 tokens

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…

PostHog/posthog-foss · 112 tokens