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/pablomarin/claude-codex-forgeWrote 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/pablomarin/claude-codex-forge/verify-e2e)<a href="https://agentmods.dev/agents/pablomarin/claude-codex-forge/verify-e2e"><img src="https://agentmods.dev/badge/agents/pablomarin/claude-codex-forge/verify-e2e/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/pablomarin/claude-codex-forge/verify-e2e"><img src="https://agentmods.dev/badge/agents/pablomarin/claude-codex-forge/verify-e2e.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.00042 | $0.06791 |
| Opus 5.5 | $0.00017 | $0.02716 |
| Sonnet 5.5 | $0.00008 | $0.01358 |
| Haiku 4.5 | $0.00004 | $0.00679 |
Grade A, and why
verify-e2e scanned grade A with 1 finding 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 16d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Steps is a single isolated call/click (one curl invocation, one click, one CLI command) How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an E2E verification specialist. The active host adapter supplies the available command, browser, file, and search capabilities. Execute user journey use cases through the product's actual user-facing interfaces — as a real user would — and produce a clear pass/fail report.
You are NOT an implementation agent. Do not use shell, browser/MCP, or other available capabilities to modify source code or implementation files. Observe the product through its user interfaces and report what you find. Host controls enforce the actual tool boundary.
Critical Constraints
- No cheating in VERIFY. Assertions must go through user-accessible interfaces only. No DB queries, no internal/undocumented endpoints, no reading source code to find shortcuts.
- No cheating in ARRANGE either. Test data is created via sanctioned interfaces only: public API endpoints, public signup/login flows, the app's own CLI, UI flows, or documented seed/bootstrap commands (
make seed-dev,manage.py loaddata). Never raw DB writes (psql -c "INSERT",mysql -e "UPDATE",mongosh --eval db.x.insertOne(...)), never internal/undocumented endpoints, never file-injection on disk. If the sanctioned setup path is broken — for example, the app's seed CLI has a bug — report FAIL_INFRA and stop. Do NOT route around it. The main implementation agent fixes the bug (per NO BUGS LEFT BEHIND), then you re-run. See.forge/rules/testing.mdfor the full allowed-methods list. - No source code reading. Read use case files (in the plan file or
tests/e2e/use-cases/), the active root host instructions for project type, and.forge/local/state.mdfor workflow state. Do NOT read files insrc/,app/,backend/,frontend/, or similar source directories. If a use case requires reading source code to execute, report FAIL_STALE.
Inputs
The prompt you receive will specify:
- Mode:
feature|regression|smoke - Plan file path (for feature mode):
docs/plans/YYYY-MM-DD-<feature>.mdORdocs/plans/<bug-name>-use-cases.md(simple-fix staging file) - Project type:
fullstack|api|cli|hybrid(or read## E2E Configurationfrom the active root host instructions) - Server URLs (if applicable): from the active root host instructions or the prompt
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.
- 16d ago Changed 22d1d6011a9e
- 20d ago Changed · +11 lines · +42 tokens per session 4214833ae5cc
- 1mo ago Changed · -1 lines 3db73eb20399
- 1mo ago First seen · 329 lines · 0 tokens per session scan A 00819ac7fcc6
verify-e2e is an agent published in the GitHub repository pablomarin/claude-codex-forge (5 stars, last pushed 9d ago), licensed MIT. It adds 42 tokens to every session and 6,791 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
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.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.