e2e-author

e2e-author is a skill for Claude Code from YoungjaeDev/my-claude-plugins. It costs 150 tokens per session (2,165 once invoked), scanned A, original, MIT.

A workflow for turning critical user journeys into Playwright end-to-end tests, which check a complete feature from the user's perspective. It uses planning and test-generation roles and follows the project's documented testing setup.

In plain words
What is it for?
Use it to plan and create tests for flows such as sign-up, checkout, or other actions where failure could affect revenue or data.
Why use it?
It reduces the manual work of deciding which important flows to test and writing their browser tests. It also checks that the required Playwright setup and project conventions exist first.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the dev plugin — 12 skills shipped together

Good fit Use it to plan and create tests for flows such as sign-up, checkout, or other actions where failure could affect revenue or data.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add YoungjaeDev/my-claude-plugins
Claude Code
/plugin install dev

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 12 skills.

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.

agentmods badge for e2e-author

README.md
[![agentmods](https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/e2e-author.svg)](https://agentmods.dev/skills/youngjaedev/my-claude-plugins/e2e-author)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 150 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,165 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00150 $0.02165
Opus 5 $0.00075 $0.01082
Sonnet 5 $0.00030 $0.00433
Haiku 4.5 $0.00015 $0.00216

Measured 2d ago against content hash 7be65b1d5910, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 2d 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.

plugins/dev/skills/e2e-author/SKILL.md · 79 lines

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 e2e-setup generated via init-agents --loop=claude (Path A); on Codex 0.135 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.md or .claude/e2e-guidelines.md) for the CUF list and conventions. If absent, run e2e-setup Step 5 or capture the CUFs inline.
  • Confirm the playwright-test .mcp.json entry and seed.spec.ts exist (both paths need them). If missing, route the user to dev:e2e-setup first.
  • 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, run e2e-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

  1. 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 0.135 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 / -generator are 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 (Codex Task). Dispatch one generic subagent per role, carrying the matching contract from ${PLUGIN_ROOT}/references/role-contracts.md inline.
    • Path C: no delegation available. Run each role yourself, in order, following the same contract with your own tools (Bash for npx playwright, the playwright-test MCP server for browser drive).

Read the full file on GitHub · 79 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.

  1. 2d ago Changed 7be65b1d5910
  2. 7d ago First seen · 79 lines · 150 tokens per session scan A 7fb275de944f

Subscribe to this mod's changes

e2e-author is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 2,165 once invoked, about $0.0007 per session on Opus 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.

Related

Other skills, from other repositories

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.

callstack/agent-device · 55 tokens

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.

warpdotdev/warp · 55 tokens

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog-foss · 112 tokens

pyats-dynamic-test

Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.

automateyournetwork/netclaw · 61 tokens

trailblaze

Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…

block/trailblaze · 115 tokens

Detox Mobile Testing

Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.

PramodDutta/qaskills · 48 tokens