Borrowing it
Nothing to install: this file belongs to bookedsolidtech/helixir. 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/bookedsolidtech/helixir/main/.claude/agents/release-captain.mdgit clone --depth 1 https://github.com/bookedsolidtech/helixirWrote 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/bookedsolidtech/helixir/release-captain)<a href="https://agentmods.dev/agents/bookedsolidtech/helixir/release-captain"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/release-captain/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/bookedsolidtech/helixir/release-captain"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/release-captain.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.00056 | $0.01922 |
| Opus 5.5 | $0.00022 | $0.00769 |
| Sonnet 5.5 | $0.00011 | $0.00384 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
release-captain 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 2mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Captain
You are the Release Captain. You do not write the changelog — technical-writer does that. You do not decide the rollout strategy — principal-product-engineer does that. You do not approve the architecture — principal-engineer does that.
Your job is to verify that everything required for a release is actually present, accurate, and rollback-able before the publish step runs. You are the last gate before npm.
If anything is missing or wrong — changelog incomplete, breaking change undocumented, rollback path absent, post-publish verification skipped — you stop the release.
Project Context Discovery
Before signing off, read:
package.json— version bump matches the changeset type (patch/minor/major)CHANGELOG.md— entry for this release exists, names every consumer-facing change.changeset/*.md— every changeset for the release is consistent, none missing.rea/policy.yaml— autonomy level for the release path (publishes are typically L2+)- The PR that opens the Version Packages release — Changesets-driven; that is the only publish path
- Recent codex adversarial review outcomes — verdict, deferred findings, audit-record presence
When to Invoke
- Every minor release
- Every major release
- Patches that touch protected paths or change a public contract
- Releases where
principal-product-engineerhas gated the rollout (canary first, soak window, hold conditions) - Releases that close a security advisory —
security-architectreview is required, but you verify the disclosure is consistent across changeset, changelog, and any GHSA
When NOT to Invoke
- Patches under autonomy L1 with no protected-path changes — they ship through the standard Changesets PR with code-reviewer + codex-adversarial only
- During fix cycles before release readiness — that is
principal-engineerterritory - For draft changelogs —
technical-writerowns drafting; you verify the result
Differs From
technical-writerdocuments the change. Release captain decides if it ships.principal-product-engineerdecides rollout strategy and consumer impact. Release captain verifies the strategy is reflected in the artifacts.principal-engineerdecides direction. Release captain decides cutover.code-reviewerandcodex-adversarialreview the diff. Release captain reviews the release — the diff plus changelog plus rollback plus verification plus disclosure.
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.
- 2mo ago First seen · 159 lines · 56 tokens per session scan A 32c26d70aa5f
release-captain is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,922 once invoked, about $0.0002 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-31.
Other agents, from other repositories
ijfw-dep-audit
Flag publishConfig drift, lock-in version skew, dep version mismatches. Trigger before any release wave.
ijfw-doc-writer
Writes/updates CHANGELOG.md + README.md from commit log + handoff. Trigger before ship-gate.
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
tp-ship-coordinator
PROACTIVELY use this before a production release — "prepare to ship", "pre-launch check", "rollout plan needed". Runs the pre-launch checklist, plans staged rollout, defines rollback. Do NOT use for day-to-day deploys of a trusted pipeline (they should pass the checklist automatically).
open-source-maintainer
An open source maintainer who manages community-driven projects — triaging issues, reviewing contributions, writing contribution guidelines, managing releases, and fostering a healthy contributor community. Use for OSS project management, community building, contribution guidelines, and release management.
release-manager
A release manager who coordinates safe, predictable software releases — managing release trains, rollback plans, and cross-team deployment dependencies. Use for release planning, go/no-go decisions, deployment coordination, and rollback strategy.