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.
npx skills add mhylle/claude-skills-collection --skill e2e-testinggit clone --depth 1 https://github.com/mhylle/claude-skills-collectionWrote 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.
[](https://agentmods.dev/skills/mhylle/claude-skills-collection/e2e-testing)<a href="https://agentmods.dev/skills/mhylle/claude-skills-collection/e2e-testing"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/e2e-testing/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.
<a href="https://agentmods.dev/skills/mhylle/claude-skills-collection/e2e-testing"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/e2e-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00124 | $0.03831 |
| Opus 5 | $0.00062 | $0.01916 |
| Sonnet 5 | $0.00025 | $0.00766 |
| Haiku 4.5 | $0.00012 | $0.00383 |
Grade A, and why
e2e-testing 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 576 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Testing Skill
Overview
A comprehensive E2E testing skill using Playwright MCP for systematic testing of any web-based system. The skill:
- Observes and reports - Never fixes issues, only documents them
- Discovers paths - Finds undocumented functionality at runtime
- Tracks history - Identifies flaky areas and suggests variations
- Produces dual reports - Human-readable and machine-readable formats
Prerequisites
Before using this skill, verify Playwright MCP is available:
- Check for
playwrightin MCP server configuration - If missing, add to Claude settings:
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest"]
}
}
}
If Playwright MCP is unavailable, inform the user and provide setup instructions before proceeding.
Mode Selection
This skill operates in three modes. Determine mode from user request:
| User Request | Mode |
|---|---|
| "Set up tests for...", "Create test regime" | Setup |
| "Run the tests", "Test the...", "Execute tests" | Run |
| "Show test results", "What failed?", "What's flaky?" | Report |
If unclear, ask: "Would you like to set up a test regime, run existing tests, or view reports?"
Setup Mode
Purpose: Create or update test regime through interactive discovery.
Entry Points
Determine entry point from user context:
| Context | Entry |
|---|---|
| User provides URL | URL Exploration |
| User describes system purpose | Description-Based |
| User points to documentation | Documentation Extraction |
| Combination of above | Combined Flow (recommended) |
Setup Workflow
Step 1: Gather Initial Context
Ask for any missing information:
- URL: Base URL of the application
- Purpose: What does this system do? (1-2 sentences)
- Key workflows: What are the critical user journeys?
- Existing docs: Any README, user stories, or specs?
Step 2: Explore Application
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 576 lines · 124 tokens per session scan A 1459060548dc
e2e-testing is a skill published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 7d ago), licensed MIT. It adds 124 tokens to every session and 3,831 once invoked, about $0.0006 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.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…