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/youngjaedev/my-claude-plugins/e2e-setupnpx skills add YoungjaeDev/my-claude-plugins --skill e2e-setupgit clone --depth 1 https://github.com/YoungjaeDev/my-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/skills/youngjaedev/my-claude-plugins/e2e-setup)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/e2e-setup"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/e2e-setup.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 | $0.00155 | $0.03878 |
| Opus 5 | $0.00077 | $0.01939 |
| Sonnet 5 | $0.00031 | $0.00776 |
| Haiku 4.5 | $0.00015 | $0.00388 |
Grade B, and why
e2e-setup scanned grade B with 1 finding 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 4d 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- Do not invent an unsupported loop. Feature-detect `--loop=codex` rather than version-guessing (`npx playwright init-agents --help | grep -qw codex`). Even when it is advertised, Codex 0.135 cannot register the generate How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Setup — full Playwright harness onboarding
Stand up Playwright's official AI test harness (planner -> generator -> healer) plus the surrounding engineering (auth separation, deterministic mocking, an E2E SSOT doc, gated CI). The harness is the point: a test run is a sensor, a test file is a spec, and the three roles form a self-improving loop. This skill only does setup + orchestration + CI + integration — it does not re-implement the roles.
Two runtime paths (Step 2). Under Claude Code,
init-agents --loop=claudegenerates the planner/generator/healer as registerable.claude/agents/*.md, ande2e-author/e2e-debugdispatch them by name (Path A). Under Codex 0.135, those generated agent files are not registerable as named subagents, so setup skips them, ensures the.mcp.jsonplaywright-testentry, and the author/debug skills run the same roles as generic subagents carrying the bundledreferences/role-contracts.md(Path B), or sequentially when no delegation is available (Path C). The engineering below (Steps 3-7) and every gate are identical on both paths.
Why this skill exists (the harness-engineering point). Installing the official agents is NOT enough — out of the box they skip auth setup, can't resolve project-known API errors, and don't know test-account usage, because they lack codebase context. Steps 3-7 below onboard them like a new hire: the config, auth scaffold, route-mock guidance, and especially the E2E SSOT doc are the context an agent needs to work autonomously. Skipping them is the usual reason "the official agents didn't just work."
Bundled templates live at
<plugin-root>/assets/. Resolve<plugin-root>with the cross-runtime block in Step 0 (ClaudeCLAUDE_PLUGIN_ROOT, Codex plugin cache) — Codex 0.135 does not exportCLAUDE_PLUGIN_ROOT, so a bare${CLAUDE_PLUGIN_ROOT}/assets/...copy fails there. The three template files areplaywright-ci.yml,e2e-guidelines.template.md,route-mock.scaffold.ts.Verified against Playwright 1.61.0 (init-agents introduced in 1.56; trace CLI in 1.59). Filenames/output below are current-version facts — Playwright's docs say agent definitions "should be regenerated whenever Playwright is updated," so re-run init-agents after upgrades.
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.
- 4d ago First seen · 170 lines · 155 tokens per session scan B ffc2e6594575
e2e-setup is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 155 tokens to every session and 3,878 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). 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
Fast headless browser for QA testing and site dogfooding. (gstack).
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
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…
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.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction using playwright-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.