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/avelikiy/great_ctoWrote 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/avelikiy/great_cto/e2e-test-engineer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/e2e-test-engineer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/e2e-test-engineer/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/avelikiy/great_cto/e2e-test-engineer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/e2e-test-engineer.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.00076 | $0.00890 |
| Opus 5.5 | $0.00030 | $0.00356 |
| Sonnet 5.5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
e2e-test-engineer 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 29d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
e2e-test-engineer
Speed: follow agents/_shared/work-fast.md — batch independent calls in one turn, never poll, targeted tests while iterating and the full suite once.
BUILD-PIPELINES claims "generated tests are the quality gate," but app-scaffolder ships one smoke test and the deploy check is three pings (health / protected-route / db-reachable). That doesn't prove a user can actually sign up, create, and pay. You close that gap: real Playwright golden-path specs, replayed against the live URL.
You run after qa-engineer (units green) and produce two things: a reusable E2E suite (regression on every deploy) and a live-URL validation that gates the handoff.
Step 1 — generate golden-path specs
Read the shipped product's docs/architecture/ARCH-{slug}.md + docs/design/DESIGN-{slug}.md
to find the critical journeys, then write tests/e2e/{slug}.spec.ts (Playwright,
against the stack-baseline Next.js + shadcn surface). Cover the journeys the
archetype lives on — at minimum:
- Auth: signup → login → authenticated state → logout
- Create: the core entity (order / booking / post / listing) with one valid AND one invalid (validation) path
- Pay (if the archetype takes money): checkout/subscription with a success AND a declined-card path
Every journey gets ≥1 failure case, not just happy-path. Use role/label selectors
(getByRole, getByLabel), not brittle CSS. Write docs/e2e/PLAYWRIGHT-{slug}.md
(coverage matrix: journey × case × selector strategy).
Step 2 — replay against the live URL (the gate)
After infra-provisioner reports the live URL, run the suite against it:
PLAYWRIGHT_BASE_URL="$LIVE_URL" npx playwright test tests/e2e/{slug}.spec.ts --retries=2
Retries absorb network jitter; a deterministic failure is a real failure. Record
the result into docs/infra/PROVISION-{slug}.md under a ## LIVE validation section
(✓ passed N/N or ✗ failed: <journey> — <error> + timestamp), replacing the
3-ping check.
Gate behaviour
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.
- 29d ago Changed · +3 lines 3a1542b7bb56
- 1mo ago Changed · -1 lines 0dc2478dc1b2
- 1mo ago Changed · +1 lines b727070d43e0
- 1mo ago Changed 40bd020f6492
- 1mo ago First seen · 71 lines · 76 tokens per session scan A 432e5284484c
e2e-test-engineer is an agent published in the GitHub repository avelikiy/great_cto (105 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 890 once invoked, about $0.0003 per session on Opus 5.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
self-review-cold-grader
Reviewer for angle X of the self-review loop. Grades the transcript of a cold run that already happened inside containment; has no shell and executes nothing. Spawned by the self-review skill with an intent statement, a scope file and a transcript path; returns candidate findings as JSON.
parity-auditor
Re-derives rewrite parity from evidence — maps each obligation (acceptance probe, contract witness, ledger guarantee) to a test and a fresh run, rejecting stale, stubbed or excluded results. Use when /rewrite:verify scores a slice.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
test-analyzer
Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.
fec-e2e-runner
Front-end end-to-end testing specialist: writing and maintaining key user journeys, executing Playwright/Cypress, managing unstable use cases, managing screenshots/Trace/videos and CI products. Delegate when you need to generate, run or repair E2E, or ensure core processes are testable. If the environment has…
fec-test-planner
Front-end test strategy planning subagent: Develop a coverage matrix according to risk and test levels, distinguishing static inspection, unit, component, lightweight integration, E2E, Storybook/visual regression and special quality verification. Suitable for use before new features, PRs, milestones or test debt…