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 commands/digi-uw/openelis-global-2/plan-record-playwrightgit clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2Wrote 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/commands/digi-uw/openelis-global-2/plan-record-playwright)<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="Measured on agentmods" 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.00000 | $0.00538 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 6d 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 — 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-videorecording 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, ordemo-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.
- Produce a concrete checklist for each flow:
-
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.tsallowlists.
- For each planned flow, invoke
-
Quality pass
- Run
/audit-playwrighton authored/updated specs. - Resolve selector and anti-pattern findings before recording.
- Run
-
Execution and recording
- Run normal validation first in target project (
core-app,core-demo,harness, orharness-demo). - Use
core-demo-video/harness-demo-videoonly for recording output. - Keep pauses/title cards project-aware (
videoPause,showTitleCard,showStepCard) so behavior is no-op outside*-demo-video.
- Run normal validation first in target project (
-
Artifact verification
- Verify
video.webmexists for each recorded flow underfrontend/test-results/<test-name>/video.webm. - If a run fails, use
/debug-playwrightwith screenshot/trace evidence.
- Verify
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.
- 6d ago First seen · 69 lines · 0 tokens per session scan A 76005cc6a57f
plan-record-playwright is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (251 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.
Other commands, from other repositories
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
vibereview
Legacy alias for the focused Randroid VibeReview skill.
visual-verify
Use Playwright MCP to visually verify the UI that was just built or modified.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
verify-pr
Verify a PR's frontend changes through browser automation.