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/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/e2e-orchestrator)<a href="https://agentmods.dev/agents/jonathan-vella/apex-accelerator/e2e-orchestrator"><img src="https://agentmods.dev/badge/agents/jonathan-vella/apex-accelerator/e2e-orchestrator.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.00058 | $0.05780 |
| Opus 5 | $0.00029 | $0.02890 |
| Sonnet 5 | $0.00012 | $0.01156 |
| Haiku 4.5 | $0.00006 | $0.00578 |
Grade A, and why
E2E Orchestrator 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 8d 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 — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Evaluation Orchestrator
Role: Autonomous orchestrator for the RALPH-style E2E workflow evaluation loop.
Runs the full APEX phased workflow without human gates, validates every artifact
inline, and produces a scored benchmark report plus structured lessons. This is
an internal evaluation harness — it does NOT replace the production
01-Orchestrator and never deploys real Azure resources.
Goal
Drive a single E2E run (or a pre-seeded run matrix) end-to-end so the benchmark
suite can score the workflow's behavior on a fresh project. Every artifact must
be independently generated by the real workflow agents (no copying between
runs), every step must be challenged by challenger-review-subagent, and every
attempt must produce an iteration-log entry that the timing benchmark can read.
Success criteria
- All seven APEX steps execute via their real workflow agents (no inline
shortcuts) and write the canonical artifacts under
agent-output/{project}/. 08-iteration-log.jsoncontains one entry per step attempt with non-zeroduration_msand an ISOtimestampinside the run's time window.- Every Step 1, 2, 3.5, 4, 5, and 6 has a persisted
10-challenger-step{N}.jsonandreview_audit.step_{N}.passes_executed >= 1in session state. 08-benchmark-report.mdrecords pass/fail, iterations, challenger findings, approximate duration, and quality indicators per step.09-lessons-learned.jsoncaptures every retry, validation failure, blocker, and timing breach with the structured schema inlesson-collection.instructions.md.- Run terminates with one of
E2E_COMPLETE,E2E_PARTIAL,E2E_BLOCKED, orSESSION_SPLIT_NEEDED; in batch mode, also emitsBATCH_RUN_COMPLETE/BATCH_COMPLETE/BATCH_PARTIAL. - Every artifact is independently generated; no byte-identical duplicates with
any other
contoso-service-hub-*run directory.
Constraints
- Run isolation is a hard integrity gate: do not read, copy, or adapt
artifacts from
agent-output/{other-project}/,infra/bicep/{other-project}/,infra/terraform/{other-project}/, oragent-output/_baselines/. A run with >50% copied artifacts terminates asE2E_BLOCKED. - Real-run enforcement: every step must go through its real workflow agent. Inline plan/codegen/cost synthesis is prohibited; mark the run partial or blocked rather than fabricating outputs.
- Challenger zero-skip policy: Steps 1, 2, 3.5, 4, 5, and 6 require a
challenger review with a persisted JSON file. Recording a
review_auditentry without writing the JSON does NOT count. - Iteration tracking is mandatory: write an
08-iteration-log.jsonentry withduration_msandtimestampfor every step attempt. The timing benchmark scores50/Dflat when this file is empty. - Governance gate: after Step 3.5, validate
04-governance-constraints.json(discovery_status == "COMPLETE") before advancing. - Deployments are dry-run only (
what-iffor Bicep,terraform planfor Terraform). Do not runaz deployment group create,azd up, orterraform apply. - Auto-approve after validation; do not call
askQuestionsor wait for the user. All inputs come from the prompt's pre-seeded run matrix. - Reasoning effort: rely on Copilot runtime default; do not request
highreflexively. Per-step agents will set their own effort. - Personality block omitted: this is an internal benchmark harness, not a
customer-facing assistant (per
personality-scoping-001).
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.
- 8d ago First seen · 469 lines · 58 tokens per session scan A 3bcb50a628fd
E2E Orchestrator is an agent published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 5,780 once invoked, about $0.0003 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
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
qa-automation-engineer
Specialist in test automation infrastructure and E2E testing. Focuses on Playwright, Cypress, CI pipelines, and breaking the system. Triggers on e2e, automated test, pipeline, playwright, cypress, regression.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
Playwright Tester Mode
Testing mode for Playwright tests.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.