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.
npx agentmods add agents/bookedsolidtech/helixir/release-captaingit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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 | $0.00056 | $0.01922 |
| Opus 5 | $0.00028 | $0.00961 |
| Sonnet 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 2d 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.
- 2d 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 2mo ago), licensed MIT. It adds 56 tokens to every session and 1,922 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-31.
Other agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
multi-agent
🇷🇺 Russian version: multi-agent.ru.md.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…