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.
git clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/playwright-setup)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/playwright-setup"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/playwright-setup/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/commands/joaquimscosta/arkhe-claude-plugins/playwright-setup"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/playwright-setup.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.00045 | $0.01117 |
| Opus 5.5 | $0.00018 | $0.00447 |
| Sonnet 5.5 | $0.00009 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
playwright-setup 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 yesterday.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/playwright-setup
Verify Playwright CLI installation and interactively create a .playwright/cli.config.json configuration file.
Step 1 — Verify CLI Installation
Run playwright-cli --version via Bash.
If installed: Report the version and proceed to Step 2.
If NOT installed: Display install instructions:
Playwright CLI is not installed.
Install it with:
npm install -g @playwright/cli@latest
Verify with:
playwright-cli --help
Then ask via AskUserQuestion:
- "Continue without CLI?" — Options: "Continue with config creation" (create the config file anyway), "Cancel setup" (stop here)
If the user cancels, stop and summarize what happened.
Step 2 — Check for Existing Config
Check if .playwright/cli.config.json exists in the project (current working directory).
If exists and valid JSON: Display current settings in a table, then ask via AskUserQuestion:
- "Config exists" — Options: "Reconfigure all settings" (proceed to Step 3), "Keep current config" (stop here)
If exists but malformed JSON: Warn the user about invalid JSON, then ask via AskUserQuestion:
- "Malformed config" — Options: "Overwrite with new config" (proceed to Step 3), "Cancel setup" (stop here)
If does not exist: Proceed to Step 3.
Step 3 — Ask Configuration Questions
Use AskUserQuestion to gather settings. Ask these essential questions together in a single call:
| # | Question | Header | Options | Default |
|---|---|---|---|---|
| Q1 | Which browser engine? | Browser | chromium, firefox, webkit | chromium |
| Q2 | Run in headless mode? | Headless | Yes (headless), No (headed) | Yes |
| Q3 | Output directory for screenshots/videos? | Output dir | .playwright-cli, ./test-results, ./playwright-output |
.playwright-cli |
Then ask whether to configure advanced settings:
| # | Question | Header | Options | Default |
|---|---|---|---|---|
| Q4 | Configure advanced settings? | Advanced | No (use defaults), Yes | No |
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.
- yesterday First seen · 137 lines · 45 tokens per session scan A 88c7ce403598
playwright-setup is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,117 once invoked, about $0.0002 per session on Opus 5.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-10-16.
Other commands, from other repositories
e2e
Generate and run E2E tests with 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.
qa
Pre-PR quality gate — browser-driven QA for web changes with a mandatory evidence packet against a provisioned environment. No QA-passed claim without artifacts. Workspace-aware. For a quick behavioral check without the evidence packet, prefer the bundled /verify or /run.
create-smoke-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.
ui-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.