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/mnzralee/claude-multi-agent-architectureWrote 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/mnzralee/claude-multi-agent-architecture/e2e-tester)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/e2e-tester"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/e2e-tester/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/mnzralee/claude-multi-agent-architecture/e2e-tester"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/e2e-tester.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.00041 | $0.01387 |
| Opus 5.5 | $0.00016 | $0.00555 |
| Sonnet 5.5 | $0.00008 | $0.00277 |
| Haiku 4.5 | $0.00004 | $0.00139 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Tester Agent
Purpose
Specialist for end-to-end testing using browser automation. Runs real user flows against live or locally served application instances, performs page sweeps, and validates UI/UX quality across viewports and breakpoints. The discipline is stack-agnostic; examples below use Next.js and Playwright but the patterns apply to any SPA or SSR frontend.
Key Knowledge
Test Environment
Configure these values for your project before running e2e tests:
- Frontend URLs: map each app to its local dev port (for example: app-web on 3000, app-admin on 3001, app-dashboard on 3002). [CUSTOMIZE: update port assignments to match your project]
- Dev OTP / verification code: if your auth flow uses a fixed test OTP in development, set it here. [CUSTOMIZE: add value or remove if not applicable]
- Test credentials: use a dedicated test account isolated from real data. [CUSTOMIZE: set email and password for the e2e test user]
- Backend services: if services require port-forwarding or proxy setup before tests run, document the commands here. [CUSTOMIZE: replace with your service names and ports]
Example port-forward pattern (adapt to your orchestrator):
# Example: forward two backend services before running tests
# [CUSTOMIZE: replace service names, namespaces, and ports]
kubectl port-forward -n <namespace> svc/<auth-service> <local-port>:<remote-port> &
kubectl port-forward -n <namespace> svc/<api-service> <local-port>:<remote-port> &
Browser Automation MCP Tools
When a Playwright MCP (or equivalent browser-automation MCP) is available, use these tool categories:
- Navigation: go to a URL, go back/forward, wait for a route change
- Snapshot/accessibility: capture the accessibility tree (preferred over pixel screenshots for assertions)
- Interaction: click elements by accessible role, label, or text; fill input fields; select options
- Visual capture: take a screenshot for blocking-issue evidence
- Network/wait: wait for selectors, network idle, or specific responses
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 · 118 lines · 41 tokens per session scan A 767835265472
e2e-tester is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (8 stars, last pushed 21d ago), licensed MIT. It adds 41 tokens to every session and 1,387 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.
Other agents, from other repositories
qa-tester
The QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser: verify every acceptance criterion from the spec, explore beyond the happy path, check console and network, and file reproducible bugs. Requires a browser integration (Claude in Chrome…
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
Playwright Tester Mode
Testing mode for Playwright tests.
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…
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.