What is plan-record-playwright?

A command for planning and running Playwright end-to-end tests, which check a complete user flow in a web browser. It reviews a feature or pull request and turns relevant flows into test work.

Use it to inspect changed files and acceptance criteria, list test flows, define steps and expected results, and coordinate tests for one or more flows.

It removes the need to decide manually which user journeys to test and how to organize them. It also coordinates planning, test writing, execution, and optional demo-video recording.

How DIGI-UW/OpenELIS-Global-2 configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to DIGI-UW/OpenELIS-Global-2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/DIGI-UW/OpenELIS-Global-2/develop/.ai/skills/playwright/commands/plan-record-playwright.md

Clone the repo

git clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/plan-record-playwright/github.svg)](https://agentmods.dev/commands/digi-uw/openelis-global-2/plan-record-playwright)

Your own site

<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/plan-record-playwright"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/plan-record-playwright/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/plan-record-playwright"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/plan-record-playwright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 538 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00538
Opus 5.5	$0.00000	$0.00215
Sonnet 5.5	$0.00000	$0.00108
Haiku 4.5	$0.00000	$0.00054

Measured 1mo ago against content hash 76005cc6a57f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-record-playwright 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 1mo 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.

.ai/skills/playwright/commands/plan-record-playwright.md · 69 lines

How it starts

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

Plan Record Playwright

Use this command to plan feature/PR scope, identify recording-worthy flows, and orchestrate authoring + execution for one or multiple Playwright E2E tests.

User Input

$ARGUMENTS

Interpret input best-effort:

/plan-record-playwright - plan from current PR/worktree context
/plan-record-playwright <feature-or-pr-scope> - plan specific scope
/plan-record-playwright --flows <csv> - plan and run a predefined flow set
/plan-record-playwright --record - include *-demo-video recording stage

Workflow

Scope triage
- Review feature/PR scope, changed files, and acceptance criteria.
- Identify candidate user flows and map each to a single test concern.
- Classify each flow as: core-app, harness, demo, or demo-video.
Flow plan
- Produce a concrete checklist for each flow:
  - route/page
  - setup data assumptions
  - user actions
  - expected assertions
  - target project
- For batches, keep one behavior per spec/test where possible.
Author tests
- For each planned flow, invoke /write-playwright-test.
- Enforce source-first selector strategy and template usage.
- Ensure each new spec is added to frontend/playwright.config.ts allowlists.
Quality pass
- Run /audit-playwright on authored/updated specs.
- Resolve selector and anti-pattern findings before recording.
Execution and recording
- Run normal validation first in target project (core-app, core-demo, harness, or harness-demo).
- Use core-demo-video / harness-demo-video only for recording output.
- Keep pauses/title cards project-aware (videoPause, showTitleCard, showStepCard) so behavior is no-op outside *-demo-video.
Artifact verification
- Verify video.webm exists for each recorded flow under frontend/test-results/<test-name>/video.webm.
- If a run fails, use /debug-playwright with screenshot/trace evidence.

Read the full file on GitHub · 69 lines

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.

1mo ago First seen · 69 lines · 0 tokens per session scan A 76005cc6a57f

Subscribe to this mod's changes

plan-record-playwright is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (272 stars, last pushed today), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 538 tokens. 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.

Browser automation E2E testing Testing carbon-design-system clinical-laboratory digital-public-goods fhir global-health health-informatics

expect

Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…

yonatangross/orchestkit · 73 tokens

OpenELIS-Global-2: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Plan Record Playwright

User Input

Workflow

What this file has done since we first saw it

Other commands, from other repositories

expect

webapp-testing

record

amazing-e2e-check

verify-pr

auto-verify