Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add YoungjaeDev/my-claude-plugins/plugin install devWrote 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-author)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/e2e-author"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/e2e-author/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/skills/youngjaedev/my-claude-plugins/e2e-author"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/e2e-author.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.00200 | $0.02540 |
| Opus 5.5 | $0.00080 | $0.01016 |
| Sonnet 5.5 | $0.00040 | $0.00508 |
| Haiku 4.5 | $0.00020 | $0.00254 |
Grade A, and why
e2e-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 13d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Author: planner -> generator orchestration
Turn a critical user flow into a reliable Playwright spec by driving the planner and generator roles. This skill orchestrates; the roles do the exploration and code generation.
Two runtime families, three execution paths, same gates: on Claude Code the roles are the named agents that e2e-setup generated via init-agents --loop=claude (Path A); on Codex those agent files are not registerable as named subagents, so each role runs as a generic subagent carrying the bundled contract from references/role-contracts.md (Path B), or in-agent sequentially when no delegation is available (Path C).
Precondition check
- Read the E2E SSOT doc (
e2e/AGENTS.mdor.claude/e2e-guidelines.md) for the CUF list and conventions. If absent, rune2e-setupStep 5 or capture the CUFs inline. - The environment seed (
seed.spec.ts, wherevere2e-setupput it) must exist (both paths need it). For app exploration, the planner/generator need at least one of:playwright-cli(re-run the probe ine2e-setupStep 1: a globalplaywright-cli, the project'snpx playwright cli, ornpx @playwright/cli@latest) or the.mcp.jsonplaywright-testentry (fallback whenplaywright-cliis unavailable). The two are independent, so having only one is enough to proceed. Route the user todev:e2e-setupfirst only whenseed.spec.tsis missing, or when bothplaywright-cliand the MCP entry are unavailable. - Path A only: confirm the named agents exist (
.claude/agents/playwright-test-planner.md,playwright-test-generator.md). If they are missing and you are on Claude Code, rune2e-setup. Do not hand-roll them. Do not demand these Claude agent files under Codex; there the bundled contracts stand in (see Step 0).
Workflow
- Resolve the plugin root + pick the execution path: run once. The resolver reaches the bundled role contracts on Path B/C; the path decision governs Steps 2-3. Tell the user which path you took in one sentence.
# Claude exports CLAUDE_PLUGIN_ROOT; Codex does not. Each branch verifies # the target (CHK) exists before committing, so a stale env falls through. CHK="references/role-contracts.md" PLUGIN_ROOT="" [ -n "${CLAUDE_PLUGIN_ROOT:-}" ] && [ -e "$CLAUDE_PLUGIN_ROOT/$CHK" ] && PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT" [ -z "$PLUGIN_ROOT" ] && [ -e "plugins/dev/$CHK" ] && PLUGIN_ROOT="plugins/dev" if [ -z "$PLUGIN_ROOT" ]; then cache_root="${CODEX_PLUGIN_CACHE:-$HOME/.codex/plugins/cache}" while IFS= read -r d; do [ -e "$d/$CHK" ] && { PLUGIN_ROOT="$d"; break; } done < <(ls -1d "$cache_root"/*/dev/*/ 2>/dev/null | awk -F/ '{print $(NF-1)"\t"$(0)}' | sort -t. -k1,1rn -k2,2rn -k3,3rn | cut -f2- | sed 's#/$##') fi { [ -n "$PLUGIN_ROOT" ] && [ -e "$PLUGIN_ROOT/$CHK" ]; } || { echo "e2e-author: role contracts not resolved (need $CHK)" >&2; exit 1; } echo "PLUGIN_ROOT=$PLUGIN_ROOT"- Path A: the named agents
playwright-test-planner/-generatorare registered (Claude Code). Dispatch them by name (Steps 2-3, unchanged). - Path B: named agents are not registerable but a generic subagent tool is available (
Agent). Dispatch one generic subagent per role, carrying the matching contract from${PLUGIN_ROOT}/references/role-contracts.mdinline. - Path C: no delegation available. Run each role yourself, in order, following the same contract with your own tools (
Bashfornpx playwright, theplaywright-testMCP server for browser drive).
- Path A: the named agents
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.
- 13d ago Changed 5b11905f7216
- 23d ago Changed 7c592cb71f29
- 1mo ago Changed · +50 tokens per session 84d72119fef3
- 1mo ago Changed 0629e5c16d31
- 1mo ago Changed 7be65b1d5910
- 2mo ago First seen · 79 lines · 150 tokens per session scan A 7fb275de944f
e2e-author is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 200 tokens to every session and 2,540 once invoked, about $0.0008 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-08-31.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.