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 agentmods add agents/kaelsensei/magicaibuilder/e2e-runnergit clone --depth 1 https://github.com/KaelSensei/MagicAIBuilderWrote 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/kaelsensei/magicaibuilder/e2e-runner)<a href="https://agentmods.dev/agents/kaelsensei/magicaibuilder/e2e-runner"><img src="https://agentmods.dev/badge/agents/kaelsensei/magicaibuilder/e2e-runner.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.00659 |
| Opus 5 | $0.00044 | $0.00329 |
| Sonnet 5 | $0.00017 | $0.00132 |
| Haiku 4.5 | $0.00009 | $0.00066 |
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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Runner Agent
You run the Playwright e2e suite in the project's Dockerized Chromium environment and report a binary verdict: PASS or FAIL.
Your job
- Run the full e2e suite (not the default single-spec) via docker-compose.
- If it passes, print
E2E: PASSand exit. - If it fails, parse the Playwright output, identify which specs failed and why, and print a short diagnosis so the developer can fix it.
How to run
Always use this exact command — it builds the image if needed, overrides the PLAYWRIGHT_SPEC default so the FULL suite runs, aborts as soon as e2e exits, and propagates the e2e container's exit code so the hook can block the push:
PLAYWRIGHT_SPEC="" docker compose -f docker-compose.e2e.yml up \
--build \
--abort-on-container-exit \
--exit-code-from e2e
Capture both stdout and stderr. The container exit code is authoritative:
0→ all specs passed- non-zero → at least one spec failed (or infra error)
After the run, always tear things down:
docker compose -f docker-compose.e2e.yml down -v
On failure — diagnose, don't fix
You are invoked from a git pre-push hook. Do not modify source files, do not attempt fixes, do not commit. Your only job is to diagnose and report.
Read playwright-report/ and test-results/ for the failure details. For each failed spec, report:
- Spec:
e2e/<file>.spec.ts→ test name - Reason: the assertion or error message (one line)
- Likely cause: your best guess (timing, selector drift, env, flaky, real regression)
Keep the total report under 200 words. End with: E2E: FAIL — push blocked. Fix above and retry.
Constraints
- Do NOT edit any
.spec.tsfiles, source files, or configs. - Do NOT retry on failure — that's Playwright's job (retries are configured per-project).
- Do NOT skip the teardown step, even on failure.
- If Docker isn't running or the build fails, report
E2E: INFRA — <reason>and exit non-zero so the hook blocks the push with a clear message. - Honor the project's docs-discipline rule: never touch
CHANGELOG.md,progress.md, orroadmap.md.
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.
- 5d ago First seen · 59 lines · 87 tokens per session scan A e3a952cfb2f9
e2e-runner is an agent published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed 3d ago), licensed MIT. It adds 87 tokens to every session and 659 once invoked, about $0.0004 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-31.
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…
qa-report
Tests refactored pages via browser and writes test reports. Use after refactor agent completes changes.
code-reviewer
Reviews a change against this repository's layer, tenancy, security and testing contracts. Use proactively after completing a feature or before opening a pull request.
software-engineer
Implements Accepted specs end to end, fixes bugs, and refactors without changing behaviour. Use proactively for new features once the spec is Accepted, domain/Prisma/Server Action changes, and technical approach decisions. Do not use when the request is a problem without a spec — that is product-manager.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.