e2e-setup

e2e-setup is a skill for Claude Code, Codex from TimothyHan/qa-buddy-skills. It costs 152 tokens per session (2,392 once invoked), scanned A, original, Apache-2.0.

A setup process for Playwright, a tool that controls a web browser to run end-to-end tests. It examines the running app, recommends testing choices, creates the test structure, and records decisions for later test work.

In plain words
What is it for?
Use it to configure browser testing, inspect authentication and available interfaces, create the playwright folder and smoke test, and document the choices for future tests.
Why use it?
It avoids repeatedly asking about details that can be discovered from the app and gives the team one shared record of how browser tests should work. It also checks that the initial setup can run.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to configure browser testing, inspect authentication and available interfaces, create the playwright folder and smoke test, and document the choices for future tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/timothyhan/qa-buddy-skills/e2e-setup
Install

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.

Any agent
npx skills add TimothyHan/qa-buddy-skills --skill e2e-setup
Clone the repo
git clone --depth 1 https://github.com/TimothyHan/qa-buddy-skills

Made for: Claude Code, Codex.

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-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/e2e-setup.svg)](https://agentmods.dev/skills/timothyhan/qa-buddy-skills/e2e-setup)
Your own site
<a href="https://agentmods.dev/skills/timothyhan/qa-buddy-skills/e2e-setup"><img src="https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/e2e-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 152 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,392 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 5 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 46
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 150
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 165
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 169
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 170
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.00152 $0.02392
Opus 5 $0.00076 $0.01196
Sonnet 5 $0.00030 $0.00478
Haiku 4.5 $0.00015 $0.00239

Measured today against content hash 8093a8401896, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

e2e-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 today.

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.

core/skills/e2e-setup/SKILL.md · 206 lines

How it starts

The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/qa-e2e-setup: Playwright Automation Setup

Configure Playwright for this team's app, once. Everything decided here is recorded in playwright/AUTOMATION.md/qa-e2e-pom and /qa-e2e-write read it on every run instead of re-asking.

Code standards: read {{REFERENCE_PATH}}/playwright-patterns.md before generating any config, fixture, or spec — it carries the decision tables, templates, and pitfalls this skill's scaffold must follow. Then the project learnings file (per the preamble) — active LRN- entries scoped here override those patterns.

Constraints

  1. Probe before asking. Anything discoverable from the running app (auth mechanism, API spec, session storage) is probed, never asked.
  2. Recommend, don't open-question. Every interview step presents a recommendation derived from the probe, marked "(Recommended)", with alternatives. Never ask "what authentication strategy would you like?" without a recommendation attached. Headless: the recommendation is the decision — record it under an Auto-decisions line in AUTOMATION.md.
  3. Every decision lands in AUTOMATION.md. If it isn't recorded, it will be re-asked later — that's a defect.
  4. Setup is done only when the scaffold has executed. npx playwright test --list must exit 0 AND the generated smoke spec must pass against the app. Until then the status is BLOCKED, not DONE.
  5. Credentials go in .env (gitignored), never in committed files or chat.

Phase 1: Inputs

Collect from the user (or the invoking context; headless: from env BASE_URL, TEST_USER, TEST_PASS, or .env):

  • App base URL (local or pre-production)
  • Test account credentials + how many test accounts exist (caps parallelism)
  • Target repo/directory for the automation code

Check for an existing setup: playwright/AUTOMATION.md present → show it and ask reconfigure-or-keep, like /qa-setup does with .qabuddy.json. Headless: keep — never reconfigure.

Phase 2: Probe the App

Read the full file on GitHub · 206 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. today Changed · +4 lines 8093a8401896
  2. 8d ago First seen · 202 lines · 152 tokens per session scan A 7d838b9f601c

Subscribe to this mod's changes

e2e-setup is a skill published in the GitHub repository TimothyHan/qa-buddy-skills (7 stars, last pushed today), licensed Apache-2.0. It adds 152 tokens to every session and 2,392 once invoked, about $0.0008 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

qawolf-cli

Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…

qawolf/cli · 118 tokens

playwright-expert

Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…

personamanagmentlayer/pcl · 77 tokens

browser-test-executor

Execute approved bounded browser Test DSL cases with fresh isolated contexts and auditable attempts. Use when running browser tests, reruns, regression checks, or blocked execution diagnostics.

dangnhit/qa-tester · 38 tokens

pw-playwright-fieldkit

Explore, debug, audit, compare, record, and test live websites with deterministic Playwright scripts and QE workflows. Use for requests to map a site, find broken pages or links, reproduce browser bugs, discover hidden or role-gated features, audit accessibility/performance, compare crawls, design or review test cases…

jpbaking/playwright-fieldkit · 143 tokens

playwright-test

Run end-to-end browser tests using the Playwright Test CLI. Create test configs, write spec files with expect assertions, execute tests with npx playwright test, and analyze results. Pre-installed with Chromium in the computer image — no setup needed. Use for E2E testing, regression testing, smoke tests, visual…

TeamDay-AI/agents · 74 tokens

playwright-cli

Automate browser interactions, test web pages and work with Playwright tests.

microsoft/playwright · 19 tokens