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 arozumenko/sdlc-skills --skill playwright-testinggit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/playwright-testing)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/playwright-testing"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/playwright-testing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.02315 |
| Opus 5 | $0.00036 | $0.01157 |
| Sonnet 5 | $0.00014 | $0.00463 |
| Haiku 4.5 | $0.00007 | $0.00231 |
Grade A, and why
playwright-testing 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 7d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Testing (live, via MCP)
Live browser testing for the manual-QA team. You drive a real browser through
the Playwright MCP server (@playwright/mcp) to explore a web app or execute a
test case step-by-step against a running app. You never write or run Playwright
test code — no Page Object Model, no pytest, no .spec.ts files. The output is
a verdict plus evidence, not a test suite.
Writing actual Playwright test code is
test-automation-engineer's job (a different factory's copy of this skill). Here, the browser is your hands.
When to use
app-profiler— explore a running web app: map key flows, capture reliable selectors and fragile areas intoapp_profile.md.test-runner— execute one webTC-NNNcase live: run each step, verify, collect evidence, return a structured result.- Web / PWA / hybrid only. Native iOS/Android → use the
mobile-testingskill. (PWA/hybrid with a mobile viewport is still this skill.)
Core loop — snapshot first
The Playwright MCP exposes browser_* tools. The loop for every check:
browser_navigate(url)— go to{{base_url}}/path(substitutebase_urlfrom the run prompt). Navigation auto-waits for load.browser_snapshot()— the accessibility snapshot gives each element atargetref plus its role and accessible name. You need the ref before you can act, and role/name is what you assert on.- Act by passing that ref as
target(plus a short human-readableelementdescription):browser_click,browser_type,browser_fill_form,browser_select_option,browser_press_key,browser_hover. browser_wait_for({text})/({textGone})— wait for the expected text to appear, or a spinner/loader text to disappear, before continuing.browser_snapshot()again, then collect evidence:browser_take_screenshot,browser_console_messages,browser_network_requests.
Refs go stale. Every target ref comes from the latest snapshot — after
any navigation or DOM change, re-browser_snapshot before acting again. The
server is versioned; this skill is written against the browser_* toolset and
parameter names can shift between @playwright/mcp releases.
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.
- 7d ago First seen · 186 lines · 71 tokens per session scan A 5a25b41b7651
playwright-testing is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 2,315 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
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…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.