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-auth-projects-and-isolationgit 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-auth-projects-and-isolation)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/playwright-auth-projects-and-isolation"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-auth-projects-and-isolation/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-auth-projects-and-isolation"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-auth-projects-and-isolation.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.00058 | $0.00641 |
| Opus 5 | $0.00029 | $0.00320 |
| Sonnet 5 | $0.00012 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
playwright-auth-projects-and-isolation 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Auth Projects And Isolation
Use this skill when the hard part is authenticated reuse or role-based test setup, not generic UI interaction.
Scope
- authentication setup projects
- storage state reuse
- role-based projects
- browser context isolation
- keeping login optimization compatible with test independence
Routing cues
- Playwright auth, login reuse,
storageState, setup project, multiple roles, admin vs user tests, browser contexts, or test isolation -> use this skill - locator and assertion problems -> use
playwright-locators-assertions-and-user-visible-contracts - suite topology or retry posture -> use
playwright-default-test-architecture - route mocking or API synchronization -> use
playwright-network-control-and-api-synchronization
Default path
- Keep each test isolated in its own browser context.
- Reuse authentication through a dedicated setup project that writes storage state.
- Create distinct storage states for materially different roles.
- Keep login helpers deterministic and small.
- Refresh or rebuild auth state when it becomes stale instead of stacking hidden recovery logic into tests.
When to deviate
- Log in within the test only when the login flow itself is the subject under test.
- Use API-level auth seeding only when it is stable, intentional, and still represents a valid user state for the UI.
- Collapse role projects only when their effective permissions and UI are truly the same.
Guardrails
- keep isolation even when auth is reused
- treat role boundaries as product contracts, not just config names
- storage state is a performance optimization, not permission logic
- setup projects should prepare auth state, not quietly perform unrelated product setup
Avoid
- sharing one mutable logged-in state across unrelated tests
- testing login in every test when the flow itself is not under test
- baking large business setup into auth bootstrap helpers
- assuming two roles can share one state file because they both can log in
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 · 76 lines · 58 tokens per session scan A b35afa160271
playwright-auth-projects-and-isolation is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 641 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
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.
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".
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.
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…