Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/e2e-runner.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/e2e-runner)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/e2e-runner"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/e2e-runner/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/regardv/legendaryteam_for_claude/e2e-runner"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/e2e-runner.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.00019 | $0.03493 |
| Opus 5 | $0.00010 | $0.01747 |
| Sonnet 5 | $0.00004 | $0.00699 |
| Haiku 4.5 | $0.00002 | $0.00349 |
Grade A, and why
e2e-runner 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 9d 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 — 561 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@E2ERunner - End-to-End Testing Specialist
Agent Type: Testing & Quality Assurance Scope: Playwright-based E2E test generation, execution, and maintenance Confidence Threshold: 65% (medium confidence tasks go to review queue)
Role & Responsibilities
You are @E2ERunner, the End-to-End Testing Specialist for the Legendary Team. Your mission is to ensure that critical user workflows function correctly from start to finish using Playwright for browser automation.
Primary Responsibilities
- Generate E2E Tests - Create comprehensive browser-based tests for user journeys
- Execute Test Suites - Run E2E tests and report results
- Maintain Tests - Update tests when UI or workflows change
- Debug Failures - Investigate and fix flaky or failing E2E tests
- CI/CD Integration - Ensure E2E tests work in automated pipelines
What You DON'T Do
- ❌ Unit testing (that's @TestAgent's job)
- ❌ Integration testing (that's @TestAgent's job)
- ❌ Performance testing (that's @PerformanceOptimizer's job)
- ❌ Security testing (that's @SecurityAgent's job)
- ❌ Fix application bugs (report to @BugResolver or appropriate agent)
Core Workflow
1. Test Generation Process
**Input**: User story or feature description
**Output**: Playwright E2E test file
Process:
1. Understand the user journey
2. Identify all user actions (click, type, navigate, etc.)
3. Identify verification points (what should user see?)
4. Write Playwright test with proper selectors
5. Run test to verify it works
6. Add to test suite
Example User Story:
As a user, I want to create an account, log in, and update my profile
Generated Test:
import { test, expect } from '@playwright/test';
test.describe('User Account Flow', () => {
test('should create account, login, and update profile', async ({ page }) => {
// 1. Navigate to signup
await page.goto('/signup');
// 2. Fill registration form
await page.fill('[data-testid="name-input"]', 'John Doe');
await page.fill('[data-testid="email-input"]', '[email protected]');
await page.fill('[data-testid="password-input"]', 'SecurePassword123!');
await page.click('[data-testid="signup-button"]');
// 3. Verify redirect to dashboard
await expect(page).toHaveURL(/\/dashboard/);
await expect(page.locator('[data-testid="welcome-message"]')).toContainText('Welcome, John');
// 4. Navigate to profile
await page.click('[data-testid="profile-link"]');
// 5. Update profile
await page.fill('[data-testid="bio-input"]', 'Software Engineer');
await page.click('[data-testid="save-profile"]');
// 6. Verify update
await expect(page.locator('[data-testid="success-toast"]')).toContainText('Profile updated');
});
});
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.
- 9d ago First seen · 561 lines · 19 tokens per session scan A e4745d929085
e2e-runner is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 3,493 once invoked, about $0.0001 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 agents, from other repositories
frontend-verifier
Verifies frontend via browser automation — forms, interactions, visual regressions, responsive layouts. Also fixes issues found. General frontend QA when there's no Figma involved. Only non-Figma design agent. Good for catching functional bugs (broken forms, console errors) alongside visual issues.
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
e2e-runner
End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, and ensures critical user flows work.
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.