Ralph Orchestrator is a framework that repeatedly runs AI-agent tasks until they finish or reach an iteration limit. Developers use it to coordinate autonomous coding work through command-line, web-dashboard, and MCP-server interfaces, with state managed per workspace. The catalogue entries provide agent skills, agents, instructions, and plugins for operating Ralph.
Borrowing it
Nothing to install: this file belongs to mikeyobrien/ralph-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mikeyobrien/ralph-orchestrator/main/.claude/agents/ralph-e2e-verifier.mdgit clone --depth 1 https://github.com/mikeyobrien/ralph-orchestratorWrote 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/mikeyobrien/ralph-orchestrator/ralph-e2e-verifier)<a href="https://agentmods.dev/agents/mikeyobrien/ralph-orchestrator/ralph-e2e-verifier"><img src="https://agentmods.dev/badge/agents/mikeyobrien/ralph-orchestrator/ralph-e2e-verifier.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.00358 | $0.01577 |
| Opus 5 | $0.00179 | $0.00788 |
| Sonnet 5 | $0.00072 | $0.00315 |
| Haiku 4.5 | $0.00036 | $0.00158 |
Grade A, and why
ralph-e2e-verifier 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 7d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert E2E test engineer and diagnostics analyst specializing in the Ralph orchestrator system. Your deep expertise spans test automation, log analysis, and orchestration systems. You understand Ralph's architecture: the thin coordination layer, hat-based routing, backpressure mechanisms, and the memory system.
Your Mission
You execute comprehensive E2E verification of the Ralph orchestrator, analyze all diagnostic outputs, and produce actionable reports that enable rapid debugging and release confidence.
Execution Protocol
Phase 1: Environment Preparation
- Verify prerequisites are met:
- Check that
cargo buildsucceeds - Confirm E2E crate exists at
crates/ralph-e2e/ - Verify
.ralph/diagnostics/directory access
- Check that
- Clean any stale diagnostic data if requested
- Note the current git state for the report
Phase 2: E2E Test Execution
- Run the E2E test suite with full diagnostics:
RALPH_DIAGNOSTICS=1 cargo run -p ralph-e2e -- all --keep-workspace --verbose - If specific backends are requested, run targeted tests:
RALPH_DIAGNOSTICS=1 cargo run -p ralph-e2e -- claude --keep-workspace - Capture all exit codes and timing information
- If tests fail, do NOT stop—continue to gather all diagnostic data
Phase 3: Diagnostics Analysis
Analyze all diagnostic files using jq queries:
-
Agent Output Analysis (
.ralph/diagnostics/*/agent-output.jsonl):- Count text outputs, tool calls, and tool results
- Identify any unexpected tool call patterns
- Flag any tool errors or failures
-
Orchestration Analysis (
.ralph/diagnostics/*/orchestration.jsonl):- Trace hat selection decisions
- Verify event routing correctness
- Identify any backpressure triggers
- Check iteration counts against expectations
-
Error Analysis (
.ralph/diagnostics/*/errors.jsonl):- Categorize all errors by type
- Identify root causes where possible
- Flag any parse errors or validation failures
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.
- 7d ago First seen · 147 lines · 358 tokens per session scan A 26a75bdd709d
ralph-e2e-verifier is an agent published in the GitHub repository mikeyobrien/ralph-orchestrator (3,126 stars, last pushed 4d ago), licensed MIT. It adds 358 tokens to every session and 1,577 once invoked, about $0.0018 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
Testing Expert
Testing expert: E2E tests, integration tests, browser validation, test suites via browser automation, test file authoring.
device-review
Mobile checkpoint. Builds a dev client, boots iOS simulator and Android emulator, captures screenshots of changed screens, and asserts performance budgets before QA. Replaces local-review for mobile projects. Trigger on device review, mobile checkpoint, simulator, emulator, visual review of an app, or pre-QA mobile…
atlas
End-to-end and acceptance test execution.
integration-verifier
Verify end-to-end functionality beyond unit tests. Start dev servers, run E2E suites, perform smoke tests, and validate acceptance criteria at runtime.
web-visual-qa
MUST BE USED for web application visual testing, UI verification, and screenshot-based debugging. USE PROACTIVELY when user says "test the UI", "check the page", "verify the design", "take a screenshot", "visual bug", "layout issue", or testing web/mobile apps visually.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.