e2e-testing-expert

e2e-testing-expert is a skill for Claude Code, Codex from roedyrustam/vibes-plug. It costs 74 tokens per session (2,646 once invoked), scanned A, original, MIT.

A testing guide for web applications using Playwright for end-to-end and component tests, and Vitest for unit and integration tests. It also covers automated testing in CI/CD systems, which run checks during software delivery.

In plain words
What is it for?
Use it to write browser tests, test React components, mock outside services, add visual regression checks, and configure testing pipelines in GitHub Actions or GitLab CI.
Why use it?
It helps replace ad-hoc testing with repeatable checks that can catch broken user flows, components, and code changes before release.

Skill for Claude CodeCodex

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

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { app } from '../src/server';.

Good fit Use it to write browser tests, test React components, mock outside services…

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/roedyrustam/vibes-plug
agentmods
npx agentmods add skills/roedyrustam/vibes-plug/e2e-testing-expert

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/e2e-testing-expert.svg)](https://agentmods.dev/skills/roedyrustam/vibes-plug/e2e-testing-expert)
Your own site
<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/e2e-testing-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/e2e-testing-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,646 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.00074 $0.02646
Opus 5 $0.00037 $0.01323
Sonnet 5 $0.00015 $0.00529
Haiku 4.5 $0.00007 $0.00265

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

Security

Grade A, and why

e2e-testing-expert 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 7d 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.

skills/e2e-testing-expert/SKILL.md · 322 lines

How it starts

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

E2E Testing Expert (Playwright 1.49+ / Vitest 3 Edition)

English | Bahasa Indonesia


English

Orchestration & Integration

Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.

Description

Expert guide for building comprehensive automated test suites using Playwright 1.49+ (E2E + component testing), Vitest 3 (unit/integration), and robust CI/CD pipelines. Covers modern testing patterns for Next.js 15, React 19, and API backends.

Trigger Conditions

  • Writing E2E tests for web applications with Playwright.
  • Writing unit or integration tests with Vitest.
  • Setting up a full automated testing pipeline in GitHub Actions / GitLab CI.
  • Testing React components in isolation with Playwright Component Testing.
  • Mocking external services (APIs, databases) in tests.
  • Setting up visual regression tests.

Playwright 1.49+ — Key Updates

New in 2026
  • aria-snapshot: Assert the accessibility tree as a snapshot — more semantic than DOM snapshots.
  • page.addLocatorHandler(): Handle dynamic UI (modals, cookie banners) automatically.
  • WebSocket testing: Built-in page.expectWebSocketEvent().
  • Playwright MCP Server: Expose a Playwright browser to AI agents via MCP tools.
Project Configuration
// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

export default defineConfig({
  testDir: './tests/e2e',
  fullyParallel: true,
  forbidOnly: !!process.env.CI,
  retries: process.env.CI ? 2 : 0,
  workers: process.env.CI ? 4 : undefined,
  reporter: [
    ['html', { open: 'never' }],
    ['junit', { outputFile: 'results.xml' }],
  ],
  use: {
    baseURL: process.env.PLAYWRIGHT_BASE_URL ?? 'http://localhost:3000',
    trace: 'on-first-retry',
    screenshot: 'only-on-failure',
    video: 'on-first-retry',
  },
  projects: [
    // Setup: seed test DB
    { name: 'setup', testMatch: /.*\.setup\.ts/ },
    {
      name: 'chromium',
      use: { ...devices['Desktop Chrome'] },
      dependencies: ['setup'],
    },
    {
      name: 'mobile-chrome',
      use: { ...devices['Pixel 7'] },
      dependencies: ['setup'],
    },
  ],
  webServer: {
    command: 'npm run dev',
    url: 'http://localhost:3000',
    reuseExistingServer: !process.env.CI,
  },
});

Read the full file on GitHub · 322 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. 7d ago First seen · 322 lines · 74 tokens per session scan A bf6cc0798844

Subscribe to this mod's changes

e2e-testing-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 2,646 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…

addyosmani/agent-skills · 68 tokens

smoke-test

Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…

tobihagemann/turbo · 88 tokens

playwright-testing

E2E testing with Playwright - Page Objects, cross-browser, CI/CD.

alinaqi/maggy · 20 tokens

limrun-android-emulator

Drive an app running on a Limrun cloud Android emulator: install an APK, launch and terminate apps with crash reports, tap, type, read the UI element tree, screenshot, record video, inject microphone audio, shape network bandwidth, and use adb over the CLI's tunnel for logcat, files, and shell. Use after a build (from…

sutchan/Agent-Skills-Hub · 147 tokens

limrun-ios-simulator

Drive an app running on a Limrun cloud iOS simulator: launch, tap, type, read the accessibility element tree, screenshot, record video, connect the app to local services, play a video file as the camera, and run timed action chains. Use after a build (from any builder) when the user wants to see, test, or interact…

sutchan/Agent-Skills-Hub · 151 tokens

limrun-detox-testing

Configure, run, or debug Detox on Limrun iOS simulators. Use when attaching the Limrun Detox runtime to an app, wiring Detox mediator connectivity, or validating app/tester connections over destination tunnels.

sutchan/Agent-Skills-Hub · 48 tokens