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 andrewsrigom/agent-skills --skill playwright-default-test-architecturegit clone --depth 1 https://github.com/andrewsrigom/agent-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/andrewsrigom/agent-skills/playwright-default-test-architecture)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/playwright-default-test-architecture"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-default-test-architecture/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/andrewsrigom/agent-skills/playwright-default-test-architecture"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-default-test-architecture.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.00066 | $0.00766 |
| Opus 5 | $0.00033 | $0.00383 |
| Sonnet 5 | $0.00013 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
playwright-default-test-architecture 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 10d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Default Test Architecture
Use this skill when the task is about the overall Playwright testing shape, not one isolated selector or one-off assertion.
Scope
- test architecture and ownership
playwright.config.tsdefaults- fixture boundaries
- browser and project strategy
- retry and parallelism posture
- routing to deeper Playwright skills
Routing cues
- adopt Playwright, structure a test suite, define projects, configure retries, choose fixture boundaries, or decide where a Playwright task belongs -> use this skill
- locators, assertions, actionability, or user-visible test contracts -> use
playwright-locators-assertions-and-user-visible-contracts - auth reuse, storage state, multi-role projects, or isolation boundaries -> use
playwright-auth-projects-and-isolation - route interception, API synchronization, request waiting, or mocking strategy -> use
playwright-network-control-and-api-synchronization - flakes, traces, codegen, debug mode, inspector, or trace viewer -> use
playwright-debugging-traces-and-flake-reduction
Default path
- Keep one
playwright.config.tsas the suite contract. - Organize tests by product surface or user journey, not by Playwright API method.
- Start with a small number of projects and add browser or device expansion only when there is real coverage value.
- Keep shared setup in fixtures and helper functions, not in ad hoc before-each sprawl.
- Prefer deterministic environment setup over compensating with retries.
- Treat retries as CI resilience, not as the primary flake fix.
When to deviate
- Split config or projects more aggressively only when the app truly has distinct runtime surfaces.
- Use more retries in CI only when infrastructure noise is real and understood.
- Add device or browser matrix breadth only when the product surface justifies the cost.
Guardrails
- tests should model user-visible behavior, not internal implementation details
- config should stay small and legible
- fixtures should centralize setup, not hide business logic
- retries should never be the first answer to instability
- browser coverage should reflect product risk, not default maximalism
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.
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.
- 10d ago First seen · 82 lines · 66 tokens per session scan A fe8720b09a07
playwright-default-test-architecture is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 766 once invoked, about $0.0003 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.
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.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…