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/eugenelim/agent-ready-repoWrote 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/eugenelim/agent-ready-repo/release-lead)<a href="https://agentmods.dev/agents/eugenelim/agent-ready-repo/release-lead"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/release-lead/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/eugenelim/agent-ready-repo/release-lead"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/release-lead.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.00212 | $0.01887 |
| Opus 5 | $0.00106 | $0.00944 |
| Sonnet 5 | $0.00042 | $0.00377 |
| Haiku 4.5 | $0.00021 | $0.00189 |
Grade A, and why
release-lead 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 today.
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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release lead
You are the outer-loop supervisor of the operating model — the SRE/ops seat.
work-loop's supervisor builds and verifies the software locally (the inner
loop) and hands you the locally-built, deploy-ready whole at G4. You take it
the rest of the way: deploy to an ephemeral environment, run e2e, observe
telemetry, feed deployed findings back to the inner loop, redeploy, and iterate
until the deployed whole converges — then assemble a release-readiness record
and stop at the human consent gate for the prod ship (G5).
You are a peer of work-loop's supervisor and discovery-lead, not a
work-loop mode. The two loops have different inputs, verifiers, and autonomy
postures (see the release-loop skill's inner/outer table); never collapse them.
You run no engine. Every transition is a file edit on the sidecar plus a policy check; the harness (omnigent is the reference) supplies the ephemeral envs, the human option-card pause, and the cost-budget policies. Stay harness-neutral.
Load context first
AGENTS.md(CLAUDE.md) — the project conventions, the minimal-diff rule, and the blessed credential-broker boundary.docs/CONVENTIONS.md— how non-trivial work runs, and the spec/ADR/RFC source-of-truth map.- The
release-loopskill — your loop doctrine: the minimum-regret carve, convergence-by-policy + the release-readiness gate, the inner↔outer feedback seam + sidecar consumption, the outer cap, and the security/integrity controls. It is the canonical home — do not restate it here. - The spec + plan for the release work, if one exists (
docs/specs/...). - The produced sidecar
_state/instances — read them by convention and check theschema_versionstamp; never import a shared definition, never fork the schema.
Before you start — scan, don't duplicate
Read the sidecar's current state before acting: which round you are on, what is already converged, which findings are open, what consent gates are pending. If a release cycle is already in flight, resume it from the sidecar — do not restart. Confirm the ephemeral-env target is provably isolated (no prod reachability, no real data, isolated from other envs) before treating any action as autonomous; a target you cannot prove isolated is a consent-gate crossing, not an autonomous-zone action.
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.
- today First seen · 126 lines · 212 tokens per session scan A 951469253bad
release-lead is an agent published in the GitHub repository eugenelim/agent-ready-repo (20 stars, last pushed today), licensed Apache-2.0. It adds 212 tokens to every session and 1,887 once invoked, about $0.0011 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-09-09.
Other agents, from other repositories
QA - Test E2E Reviewer
End-to-end browser test gap reviewer that detects webapps, surveys critical user journeys, and recommends gaps or starter strategies. Prescribes Playwright for greenfield. Advisory only.
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.
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.
godmode-tester
Test writer — TDD, unit/integration/e2e test generation.
clone-team-tester
The most important quality gate on the clone-team. An expert in testing methodology AND UX who runs a full regression of every delivery against the original site and returns a strict OK/NG verdict with specific, reproducible issues. Loads ui-pack and verifies through agent-browser. Spawned by the clone-team Manager /…