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 agentmods add skills/evolplus/talos/playwright-authornpx skills add evolplus/talos --skill playwright-authorgit clone --depth 1 https://github.com/evolplus/talosWhat 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 | $0.00076 | $0.03325 |
| Opus 5 | $0.00038 | $0.01663 |
| Sonnet 5 | $0.00015 | $0.00665 |
| Haiku 4.5 | $0.00008 | $0.00332 |
Grade A, and why
playwright-author 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 2d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Author
When to use
You are QA-Author writing an executable spec for a web UI surface. The ui-test-execution skill gave you the cross-runner principles; this skill is the Playwright-specific procedure. Consult both: ui-test-execution for the contract, playwright-author for the implementation.
Use this skill only when:
- Surface is web (per SRS §3.4.2 UI Introspection Profile row's Framework column).
- Project uses Playwright (the org default per
solution-defaults; otherwise an ADR justifies the deviation). - You have the markdown TCs in hand and need to produce the matching
.spec.tsfiles.
Inputs and outputs
- Inputs: markdown TCs (under
docs/test-cases/by-us/<US-NNN>/ordocs/test-cases/by-task/<task-id>/), instrumentation contract (docs/instrumentation-contract.md), visual spec (docs/uiux/visual-specs/<task-id>.md) for structural cases, frozen API contract for API-touching flows - Outputs: one
.spec.tsfile per US (or per task layer), onetest()per TC, page objects undere2e/pages/when reuse warrants, fixtures undere2e/fixtures/
Project layout convention
<repo-root>/
├── e2e/
│ ├── playwright.config.ts
│ ├── specs/
│ │ ├── by-us/
│ │ │ └── us-001-spectator-join.spec.ts
│ │ └── by-task/
│ │ └── t-014/
│ │ ├── api.spec.ts
│ │ ├── e2e.spec.ts
│ │ └── structural.spec.ts
│ ├── pages/ (page object models — one class per screen)
│ │ └── spectator-live-view.page.ts
│ ├── fixtures/ (test data + setup)
│ │ ├── users.ts (test users by role)
│ │ ├── matches.ts (DB seed factories)
│ │ └── api-mocks/ (network response mocks)
│ └── utils/ (shared helpers)
│ ├── auth.ts (login flow as a fixture, not a re-tested flow)
│ └── waits.ts (condition-based waits)
└── package.json (playwright as devDependency)
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.
- 2d ago First seen · 290 lines · 76 tokens per session scan A 4a16f549ba94
playwright-author is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 76 tokens to every session and 3,325 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.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
e2e-deployment-skill
Use this deployment skill to verify shared skills load during Playwright startup.
launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…
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.
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
web-preview
Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.