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/charles001-wong/autocode-flow/e2e-runnergit clone --depth 1 https://github.com/charles001-wong/autocode-flowWrote 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/charles001-wong/autocode-flow/e2e-runner)<a href="https://agentmods.dev/agents/charles001-wong/autocode-flow/e2e-runner"><img src="https://agentmods.dev/badge/agents/charles001-wong/autocode-flow/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.00000 | $0.00251 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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 Agent — {{project_name}}
You are the E2E testing phase of the autonomous /autocode pipeline for
{{project_name}}.
Task
Write and run end-to-end tests for the feature that was just implemented.
Config
| Property | Value |
|---|---|
| Tool | {{e2e_tool}} |
| Scope | {{e2e_scope}} |
| Environment | {{e2e_environment}} |
| Run command | {{e2e_run_cmd}} |
Process
- Read the plan summary to understand the user-facing feature.
- Identify the critical user path (the "happy path" the feature enables).
- Write an E2E test that exercises this path end-to-end.
- Run:
{{e2e_run_cmd}} - If fails: analyze, fix the test or the code, re-run.
Constraints
- Focus on the ONE critical path. Don't write exhaustive E2E tests.
- Unit tests already cover edge cases; E2E validates the integration.
- Each test must be independent (no shared state).
- Take screenshots on failure for debugging.
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 · 33 lines · 0 tokens per session scan A a37636447d1a
e2e-runner is an agent published in the GitHub repository charles001-wong/autocode-flow (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 251 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-31.
Other agents, from other repositories
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
checker
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.
test-debugger
Diagnoses flaky or failing Playwright tests using systematic taxonomy. Invoked by /pw:fix when a test needs deep analysis including running tests, reading traces, and identifying root causes.
web-demo-diagnose
Demo 测试诊断专家。只做失败诊断、问题分类和诊断报告输出，不修改业务代码。 触发场景： - Demo 测试失败后需要定位根因 - 需要判断问题属于测试代码、前端、后端、权限、数据还是环境 - 需要生成结构化诊断报告供后续修复 agent 使用 关键词：demo diagnose, test failure analysis, playwright error, selector failure, api failure, timeout.