agent-e2e-test-specialist

agent-e2e-test-specialist is a skill for Claude Code from travisjneuman/.claude. It costs 76 tokens per session (2,679 once invoked), scanned A, original, MIT.

An end-to-end testing specialist for testing complete user flows in browsers with Playwright or Cypress. End-to-end tests check an application from the user's interface through its connected services.

In plain words
What is it for?
Use it to create and maintain browser tests, mock network calls, compare screenshots, test components, and check accessibility during user flows.
Why use it?
It helps catch broken workflows and visual changes that unit tests, which check smaller pieces of code, may miss.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter. Also seen: agent in frontmatter; mentions subagents.

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

Good fit Use it to create and maintain browser tests, mock network calls, compare screenshots, test components, and check accessibility during user flows.

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/travisjneuman/.claude
agentmods
npx agentmods add skills/travisjneuman/.claude/agent-e2e-test-specialist

Made for: Claude Code.

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 agent-e2e-test-specialist

README.md
[![agentmods](https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-e2e-test-specialist/github.svg)](https://agentmods.dev/skills/travisjneuman/.claude/agent-e2e-test-specialist)
Your own site
<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-e2e-test-specialist"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-e2e-test-specialist/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.

agentmods 80×15 button for agent-e2e-test-specialist

Your own site · 80×15
<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-e2e-test-specialist"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-e2e-test-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,679 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.00076 $0.02679
Opus 5.5 $0.00030 $0.01072
Sonnet 5.5 $0.00015 $0.00536
Haiku 4.5 $0.00008 $0.00268

Measured 14d ago against content hash d621d9b5db39, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-e2e-test-specialist 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 14d 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/agent-e2e-test-specialist/SKILL.md · 410 lines

How it starts

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

E2E Test Specialist Agent

Use this skill only when the user explicitly asks for tests; otherwise validate by reviewing the diff and the code it touches. Browser automation installs (Playwright, Cypress browsers) run only through an environment the user has approved for them.

Expert end-to-end testing engineer specializing in Playwright, Cypress, visual regression testing, and browser automation with emphasis on reliability and maintainability.

Capabilities

Playwright

  • Multi-browser testing (Chromium, Firefox, WebKit)
  • Auto-wait and smart assertions
  • Network interception and mocking
  • Codegen for test scaffolding
  • Trace viewer for debugging
  • Parallel test execution
  • Component testing

Cypress

  • Component and E2E testing
  • cy.intercept for API mocking
  • Custom commands and utilities
  • Cypress Dashboard integration
  • Real-time test runner

Visual Regression

  • Playwright screenshot comparison
  • Percy integration (cross-browser visual diffs)
  • Chromatic for Storybook components
  • Threshold-based matching
  • Baseline management

Accessibility in E2E

  • axe-core integration with Playwright/Cypress
  • WCAG violation detection in test flows
  • Automated accessibility audits per page

CI/CD Integration

  • GitHub Actions with Playwright
  • Parallel test sharding
  • Artifact collection (videos, traces, screenshots)
  • Flaky test detection and retry strategies

Test Architecture

  • Page Object Model (POM)
  • Component Object Model
  • Test data factories
  • Fixture management
  • Environment-aware configuration

When to Use This Agent

  • Setting up E2E testing infrastructure from scratch
  • Writing new E2E tests for features
  • Debugging flaky or failing E2E tests
  • Adding visual regression testing
  • Integrating E2E tests into CI/CD
  • Migrating from Cypress to Playwright (or vice versa)
  • Adding accessibility testing to E2E suite

Instructions

When working on E2E tests:

  1. Choose the right tool: Default to Playwright for new projects (multi-browser, faster). Use Cypress if the project already uses it.
  2. Page Object Model: Always structure tests with POM for maintainability. One page class per major page or component group.
  3. Test independence: Each test should be able to run in isolation. No shared state between tests. Use fixtures for setup.
  4. Avoid sleep/wait: Use Playwright's auto-wait or explicit waitFor conditions. Never use arbitrary setTimeout or cy.wait(ms).
  5. Test user flows, not implementation: Focus on what the user sees and does, not internal component state.

Read the full file on GitHub · 410 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. 14d ago First seen · 410 lines · 76 tokens per session scan A d621d9b5db39

Subscribe to this mod's changes

agent-e2e-test-specialist is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 2,679 once invoked, about $0.0003 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-09-30.

Related

Other skills, from other repositories

qa-e2e

End-to-end tests with Playwright or Cypress. Trigger when the user wants to create user journey tests, UI integration tests, or browser automation.

christopherlouet/claude-base · 34 tokens

qa-chrome

Visual tests and browser debugging via Chrome. Use to test web pages, verify visual rendering, debug with the console, or automate browser actions. Trigger when the user mentions "visual test", "Chrome", "browser", "browser console", "DOM", "screenshot", "GIF".

christopherlouet/claude-base · 61 tokens

memstack-development-webapp-testing

Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.

cwinvestments/memstack · 75 tokens

playwright

Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.

Mindrally/skills · 26 tokens

playwright-cursor-rules

Expert guidance for Playwright end-to-end testing with TypeScript and JavaScript best practices.

Mindrally/skills · 24 tokens

playwright-ops

Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer, flaky test, test sharding, visual regression, toHaveScreenshot…

0xDarkMatter/claude-mods · 85 tokens