e2e-testing

e2e-testing is a skill for Claude Code, Codex from drvoss/everything-copilot-cli. It costs 38 tokens per session (1,526 once invoked), scanned A, original, MIT.

A way to test complete user journeys through a running application, such as signing in, creating something, or making a purchase. These end-to-end tests check that the connected parts work together.

In plain words
What is it for?
Use it to create Playwright or Cypress tests for critical paths, edge cases, smoke checks, and regression coverage.
Why use it?
It catches workflow failures that can remain hidden even when individual units of code pass their tests.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/drvoss/everything-copilot-cli/e2e-testing
Any agent
npx skills add drvoss/everything-copilot-cli --skill e2e-testing
Clone the repo
git clone --depth 1 https://github.com/drvoss/everything-copilot-cli

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/e2e-testing.svg)](https://agentmods.dev/skills/drvoss/everything-copilot-cli/e2e-testing)
Your own site
<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/e2e-testing"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/e2e-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00038 $0.01526
Opus 5 $0.00019 $0.00763
Sonnet 5 $0.00008 $0.00305
Haiku 4.5 $0.00004 $0.00153

Measured yesterday against content hash 879919a7a5bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

e2e-testing scanned grade A 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s http://localhost:3000/health
skills/testing/e2e-testing/SKILL.md · 213 lines

How it starts

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

End-to-End Testing

When to Use

  • Validating critical user journeys work from start to finish
  • After major refactors that may break integration between components
  • Before releases to verify the full system works together
  • When unit tests pass but users report bugs in real workflows
  • Setting up regression tests for frequently broken features

Prerequisites

  • Application can be started in a test/dev environment
  • E2E test framework installed (Playwright, Cypress, Selenium, etc.)
  • Test data and fixtures available or can be seeded
  • Understanding of the most important user workflows

Workflow

1. Identify Critical User Paths

Map the workflows that must always work:

# Find existing E2E tests to understand what's covered
glob pattern="**/*.e2e.*"
glob pattern="**/e2e/**/*.{ts,js}"
glob pattern="**/cypress/**/*.{ts,js}"
glob pattern="**/playwright/**/*.{ts,js}"

Prioritize paths by business impact:

Priority Path Example
🔴 P0 Revenue-critical Signup → Purchase → Confirmation
🔴 P0 Authentication Login → Access protected resource
🟡 P1 Core features Create item → Edit → Delete
🟡 P1 Data integrity Import → Transform → Export
🟢 P2 Secondary flows Settings → Profile update

2. Set Up the Test Environment

# Start the application in test mode
$env:NODE_ENV="test"
npm run dev  # mode: async, detach: true

# Seed test data
npm run db:seed:test 2>&1

# Verify the app is running
curl -s http://localhost:3000/health

3. Write E2E Tests

Playwright example:

// e2e/auth.spec.ts
import { test, expect } from '@playwright/test';

test.describe('Authentication Flow', () => {
  test('user can sign up and log in', async ({ page }) => {
    // Navigate to signup
    await page.goto('/signup');

    // Fill the form
    await page.fill('[name="email"]', '[email protected]');
    await page.fill('[name="password"]', 'SecurePass123!');
    await page.click('button[type="submit"]');

    // Verify redirect to dashboard
    await expect(page).toHaveURL('/dashboard');
    await expect(page.locator('h1')).toContainText('Welcome');
  });

  test('shows error for invalid credentials', async ({ page }) => {
    await page.goto('/login');
    await page.fill('[name="email"]', '[email protected]');
    await page.fill('[name="password"]', 'wrong');
    await page.click('button[type="submit"]');

    await expect(page.locator('.error')).toContainText('Invalid credentials');
    await expect(page).toHaveURL('/login');
  });
});

Read the full file on GitHub · 213 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. yesterday First seen · 213 lines · 38 tokens per session scan A 879919a7a5bc

Subscribe to this mod's changes

e2e-testing is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 38 tokens to every session and 1,526 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

copilotd-e2e-verification

Perform real end-to-end validation of copilotd issue and pull request orchestration using live GitHub artifacts.

DamianEdwards/copilotd · 31 tokens

journey-runner

Run an agentic journey end-to-end: preflight the host, extract prompts, execute them in an isolated workspace, build, deploy to Azure, verify with real requests and screenshots, and clean up only owned resources. USE FOR: test a journey, run a journey end-to-end, validate journey prompts, deploy a journey to Azure…

DanWahlin/github-azure-agentic-journeys · 113 tokens

journey-test-harness

Run multiple journeys as a cross-platform test suite. Discover journeys, invoke journey-runner in isolated workspaces, deploy, verify, capture screenshots, clean up only owned Azure resources, and produce a consolidated report. USE FOR: test all journeys, regression test, CI journey validation, nightly journey test…

DanWahlin/github-azure-agentic-journeys · 109 tokens

testing-with-marionette

AI-driven Flutter E2E testing via VM Service CLI. Control running Flutter apps in debug mode for smoke tests, regression checks, exploratory testing, and UI automation. Trigger when user mentions E2E testing, UI automation, smoke tests, integration testing, test automation, controlling Flutter apps, VM Service…

Poorgramer-Zack/dart-expert-skills · 158 tokens

flutter-testing

Covers Flutter testing across all three layers: unit tests (business logic, ViewModels, repositories), widget tests (UI rendering, interactions, golden regression), and integration/E2E tests (full app flows, native OS interactions). Use this skill when writing any Flutter test, setting up mocking with mocktail or…

Poorgramer-Zack/dart-expert-skills · 137 tokens

external-site-profile-learning

Use this skill when investigating, adding, validating, or debugging external website profiles for the 99idea Playwright browser demo. It teaches how to probe selectors, classify failure modes, add config-driven profiles, and validate both heuristic and Gemini flows.

AllenS0104/skill-browser · 54 tokens