A test-running skill for Playwright end-to-end tests, which test a complete application flow in a browser. It detects the right test project from a name, alias, file, or folder before running the tests.

Use it to run named, aliased, or path-based E2E test targets, including admin or creator test projects, with the detected Playwright configuration.

It removes the need to manually select the Playwright project and includes checks intended to avoid database connection problems during testing.

e2e-run — Skill for Claude Code by parisgroup-ai/imersao-ia-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 parisgroup-ai/imersao-ia-setup --skill e2e-run

Clone the repo

git clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setup

Made for: Claude Code.

Or install imersao, the plugin that ships this one along with the rest of its 74 skills, 7 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/e2e-run/github.svg)](https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/e2e-run)

Your own site

<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/e2e-run"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/e2e-run/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/e2e-run"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/e2e-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 748 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.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.00748
Opus 5.5	$0.00021	$0.00299
Sonnet 5.5	$0.00011	$0.00150
Haiku 4.5	$0.00005	$0.00075

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

Security

Grade A, and why

e2e-run 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 1mo 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.

plugins/imersao/skills/e2e-run/SKILL.md · 106 lines

How it starts

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

e2e-run - Smart E2E Test Runner

Run E2E tests with automatic project detection and optimized wait strategies.

Usage

/e2e-run <target>           # Run tests for target
/e2e-run admin-tests        # Exact project match
/e2e-run admin              # Fuzzy match → admin-tests
/e2e-run creator-detail     # File match → detects project from path

Project Auto-Detection

Read apps/web/e2e/e2e-projects.json to detect the correct --project flag:

Exact match: Input matches project name → use directly
Alias match: Input matches an alias → resolve to project
Path match: Input is a file/folder → find project by testMatch pattern
Default: Use chromium for unknown inputs

Execution Steps

Step 1: Detect Project

# Read config
cat apps/web/e2e/e2e-projects.json

Determine --project=<detected> based on input.

Step 2: Pre-flight Check

# Check DB connections (avoid pool exhaustion)
docker exec -i cursos-postgres psql -U postgres -c \
  "SELECT count(*) FROM pg_stat_activity WHERE datname = 'cursos';" 2>/dev/null || echo "0"

If count > 80: docker restart cursos-postgres && sleep 5

Step 3: Execute Tests

pnpm test:e2e --project=<detected> --reporter=list 2>&1 | tee /tmp/e2e-run-output.txt

Step 4: Generate Structured Output

After execution, create apps/web/e2e-run-result.yaml:

executed_at: <ISO8601>
project: <detected>
target: <original-input>
duration_seconds: <time>
total: <count>
passed: <count>
failed: <count>
failures:
  - test: "<file>:<line>"
    title: "<test title>"
    error_summary: "<first line of error>"
    error_context: "<path to error-context.md>"
    category: "<auto-detected category>"

Category Auto-Detection

Read apps/web/e2e/e2e-categories.json and match error patterns:

"page.goto: 404"       → missing-route
"locator.click: timeout" → missing-element
"networkidle" + "403"  → timeout-403
"response.toBeOK"      → api-error

Read the full file on GitHub · 106 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.

1mo ago First seen · 106 lines · 53 tokens per session scan A efa273789856

Subscribe to this mod's changes

e2e-run is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 20d ago), licensed MIT. It adds 53 tokens to every session and 748 once invoked, about $0.0002 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-08-31.

Claude Code E2E testing Testing ai-skills automation bootcamp claude-code-plugin e2e pg-tooling

proof-e2e

Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".

tonone-ai/tonone · 63 tokens

e2e-testing

End-to-end testing for Falcon Foundry apps using Playwright and @crowdstrike/foundry-playwright. TRIGGER when user asks to "add e2e tests", "add playwright tests", "write end-to-end tests", "test my app", or mentions "e2e", "playwright", or "end-to-end" in the context of testing a Foundry app. DO NOT TRIGGER during…

CrowdStrike/foundry-skills · 116 tokens

browser-validator

Automatically validate implementations in real browsers after code is written or when user says "test this", "test what you built in the browser", "check it in a real browser", or "validate at the breakpoints". Uses Chrome DevTools MCP to test responsive breakpoints (320px, 768px, 1024px), check accessibility…

kanopi/cms-cultivator · 99 tokens

test-scaffolding

Automatically generate test scaffolding when user writes new code without tests or mentions needing tests. Supports unit, integration, e2e, and data tests for PHP and JavaScript. Invoke when user mentions "tests", "testing", "coverage", "write tests", or shows new untested code.

kanopi/cms-cultivator · 64 tokens

Test Engineer

Creates or completes a medium-coverage test suite: unit, component, and critical e2e flows.

Tariux/AI-Skills-Not-Awesome · 24 tokens

feature-acceptance

A browser-based acceptance testing process that compares an online implementation with a product requirements document and, when available, an HTML prototype. It records what is complete, partial, missing, or inconsistent, with screenshots and prioritized blockers.

mayuemarsha-del/pm-skills · 192 tokens