e2e-tester

e2e-tester is a skill for Claude Code, Codex from PageAI-Pro/ralph-loop. It costs 35 tokens per session (4,262 once invoked), scanned A, a copy of playwright, MIT.

A guide for writing Playwright end-to-end tests, which test a complete user journey through a real web interface. It covers reusable page objects, reliable selectors, and checking existing flows before adding tests.

In plain words
What is it for?
Use it to explore a web flow, verify forms and page transitions, capture expected states, and create Playwright tests with confirmed selectors.
Why use it?
It helps prevent inaccurate or fragile tests by basing them on the actual interface and choosing end-to-end tests only when they add value.

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/pageai-pro/ralph-loop/e2e-tester
Any agent
npx skills add PageAI-Pro/ralph-loop --skill e2e-tester
Clone the repo
git clone --depth 1 https://github.com/PageAI-Pro/ralph-loop

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/pageai-pro/ralph-loop/e2e-tester.svg)](https://agentmods.dev/skills/pageai-pro/ralph-loop/e2e-tester)
Your own site
<a href="https://agentmods.dev/skills/pageai-pro/ralph-loop/e2e-tester"><img src="https://agentmods.dev/badge/skills/pageai-pro/ralph-loop/e2e-tester.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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.00035 $0.04262
Opus 5 $0.00017 $0.02131
Sonnet 5 $0.00007 $0.00852
Haiku 4.5 $0.00003 $0.00426

Measured 5d ago against content hash 2303afc9222f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

e2e-tester 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 5d 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.

Origin

This is a copy

92% identical to playwright — 311 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agent/skills/e2e-tester/SKILL.md · 596 lines

How it starts

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

Before you start:

  • check if any existing tests cover the functionality you are testing
  • check if a unit tests can cover the feature better
  • analyze if a end to end test brings any value over a unit test

If the answer is yes to any of the above, proceed with the end to end test creation.

MCP Workflow (MANDATORY If Available)

⚠️ If you have Playwright MCP tools, ALWAYS use them BEFORE creating any test:

  1. Navigate to target page
  2. Take snapshot to see page structure and elements
  3. Interact with forms/elements to verify exact user flow
  4. Take screenshots to document expected states
  5. Verify page transitions through complete flow (loading, success, error)
  6. Document actual selectors from snapshots (use real refs and labels)
  7. Only after exploring create test code with verified selectors

If MCP NOT available: Proceed with test creation based on docs and code analysis.

Why This Matters:

  • ✅ Precise tests - exact steps needed, no assumptions
  • ✅ Accurate selectors - real DOM structure, not imagined
  • ✅ Real flow validation - verify journey actually works
  • ✅ Avoid over-engineering - minimal tests for what exists
  • ✅ Prevent flaky tests - real exploration = stable tests
  • ❌ Never assume how UI "should" work

Waiting Strategies (CRITICAL)

// ❌ NEVER use fixed waits
await page.waitForTimeout(2000);

// ✅ Wait for specific conditions
await expect(element).toBeVisible();
await page.waitForResponse(resp => resp.url().includes('/api/data'));
await page.waitForURL('**/dashboard');
await expect(page.getByText('Success')).toBeVisible({ timeout: 10000 });

// ✅ For SPAs, prefer explicit waits over networkidle
await page.goto('/app', { waitUntil: 'domcontentloaded' });
await expect(page.getByRole('main')).toBeVisible();

File Structure

tests/
├── base-page.ts              # Parent class for ALL pages
├── helpers.ts                # Shared utilities
└── {page-name}/
    ├── {page-name}-page.ts   # Page Object Model
    ├── {page-name}.spec.ts   # ALL tests here (NO separate files!)
    └── {page-name}.md        # Test documentation

Read the full file on GitHub · 596 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. 5d ago First seen · 596 lines · 35 tokens per session scan A 2303afc9222f

Subscribe to this mod's changes

e2e-tester is a skill published in the GitHub repository PageAI-Pro/ralph-loop (295 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 4,262 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to playwright, differing in 311 lines, and is treated as a copy.