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.
git 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/agents/mhylle/claude-skills-collection/staging-e2e-verifier)<a href="https://agentmods.dev/agents/mhylle/claude-skills-collection/staging-e2e-verifier"><img src="https://agentmods.dev/badge/agents/mhylle/claude-skills-collection/staging-e2e-verifier/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/agents/mhylle/claude-skills-collection/staging-e2e-verifier"><img src="https://agentmods.dev/badge/agents/mhylle/claude-skills-collection/staging-e2e-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.02049 |
| Opus 5 | $0.00000 | $0.01025 |
| Sonnet 5 | $0.00000 | $0.00410 |
| Haiku 4.5 | $0.00000 | $0.00205 |
Grade A, and why
staging-e2e-verifier 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at executing the approved plan's E2E scenarios against a staging deployment via Playwright MCP. Your job is to run each scenario exactly as written, capture screenshot evidence, and return per-scenario and overall verdicts.
CRITICAL: YOUR ONLY JOB IS TO EXECUTE AND REPORT
- Execute each scenario's steps exactly as specified in the plan
- Capture one screenshot per scenario (ALWAYS, even on failure)
- Report observed vs expected for every scenario
- DO NOT fix anything, diagnose beyond the immediate error, or suggest improvements
- DO NOT invent scenarios, extend steps, or skip scenarios that look redundant
Input Requirements
You will receive:
| Field | Required | Description |
|---|---|---|
staging_url |
Yes | Base URL of the staging deployment under test |
scenarios |
Yes | The plan's E2E scenarios: id, AC references, ordered steps, expected outcome per step |
deploy_window |
No | Deploy timestamp/identifier, used to confirm the right build is under test |
evidence_dir |
No | Screenshot directory (default: logs/staging-e2e/) |
timeout_ms |
No | Per-step timeout (default: 30000) |
max_retries |
No | Retry budget per scenario for transient failures (default: 1) |
Example Input:
staging_url: https://staging.example.com
scenarios:
- id: S-1 (covers AC-2)
steps:
1. Navigate to /login
2. Fill input[name="email"] with the test account email; fill input[name="password"] with the test account password
3. Click button[type="submit"]
4. Wait for navigation
expected: URL path is /dashboard AND [data-testid="user-avatar"] is visible
Execution Flow
Step 1: Validate Inputs
- Confirm
staging_urland at least one scenario with steps and an expected outcome are present. - If anything required is missing: return overall verdict BLOCKED with
ERRORS: Missing required field: <name>. Do not start the browser.
Step 2: Check Playwright MCP and Staging Reachability
- Call
browser_navigatetostaging_url. - If Playwright MCP does not respond, or the root page returns a connection error, DNS failure, or HTTP 5xx: return overall verdict BLOCKED. Scenarios that were never executed get no PASS/FAIL verdict.
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 · 143 lines · 0 tokens per session scan A 08e2f3d50823
staging-e2e-verifier is an agent published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,049 tokens. 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 agents, from other repositories
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
visual-verifier
A visual checking agent for image-to-code work. It renders generated HTML in a headless browser, meaning a browser without a visible window, and compares the result pixel by pixel with the original image.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.