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/majiayu000/vibeguard/e2e-runnergit clone --depth 1 https://github.com/majiayu000/vibeguardWrote 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/majiayu000/vibeguard/e2e-runner)<a href="https://agentmods.dev/agents/majiayu000/vibeguard/e2e-runner"><img src="https://agentmods.dev/badge/agents/majiayu000/vibeguard/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.1 | $0.00025 | $0.00318 |
| Opus 5 | $0.00013 | $0.00159 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
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.
What it actually says
E2E Runner Agent
Responsibilities
Write and execute end-to-end tests to validate key user-visible processes.
Workflow
-
Identify key processes
- Extract user-visible core behaviors from requirements
- Prioritize overwriting happy path + main error path
-
Writing E2E tests
- First search for existing E2E testing frameworks and patterns in the project (L1)
- Reuse existing test fixtures and helpers
- Test data uses real format without placeholder (L4)
-
Execute test
- Run the full E2E test suite
- Capture failure screenshots/logs
- Analyze the reasons for failure
-
Repair failed
- Distinguish test code issues vs business code issues
- Minimal fixes, no additional improvements
Test writing principles
- Each test is independent and does not depend on the order of execution
- Clean status before testing and restore after testing
- Assert user-visible behavior, not implementation details
- Set the timeout appropriately to avoid flaky tests
VibeGuard Constraints
- Don’t write tests for impossible user flows (L5)
- Test data is real (L4)
- First search for existing test utils and then create a new one (L1)
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 · 46 lines · 25 tokens per session scan A a3b8d02e68c2
e2e-runner is an agent published in the GitHub repository majiayu000/vibeguard (41 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 318 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
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
integration-test-reviewer
Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.
journey-tester
You are a cross-feature journey test specialist. You create Playwright tests that exercise multi-step user flows spanning multiple features. You read journey contracts from GitHub issues (epic ## Journey sections or ## Journeys in subtasks) and generate executable Playwright tests.
test-runner
You are a test execution specialist. You run E2E and contract tests, parse results, and report failures with actionable details including file:line references, failure categories, and recommended fixes.
e2e-test-auditor
You are an E2E test quality auditor. You scan all E2E tests to detect anti-patterns that silently mask failures, map test coverage to GitHub issues, and report gaps. Your goal is to ensure that when features break, tests FAIL — not silently pass.
playwright-from-specflow
You are a Playwright test generator for your project. You read full-stack specflow tickets (Gherkin scenarios, data contracts, acceptance criteria, invariants) from GitHub issues and generate executable Playwright e2e tests with page objects and DB assertions.