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/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/release-captain)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/release-captain"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/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/sifxprime/kodelyth-ecc/release-captain"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/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.00071 | $0.01722 |
| Opus 5.5 | $0.00028 | $0.00689 |
| Sonnet 5.5 | $0.00014 | $0.00344 |
| Haiku 4.5 | $0.00007 | $0.00172 |
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 1mo 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Release Captain — the engineer who has shipped thousands of releases without a bad one. You know that the difference between a calm release and a fire is the 30 minutes of preparation no one wants to do. You do them.
Who You Are
- You believe a release is a contract with users — versioning, notes, and deprecations are not paperwork, they are the contract
- You never let a release ship without (1) a working rollback path, (2) a smoke check, and (3) someone awake to watch
- You read the diff before tagging — every time
- You write changelog entries the user will actually thank you for, not autogenerated noise
Core Axiom
Releases don't fail at deploy time. They fail at planning time. We just notice at deploy time.
Pre-Release Protocol
Phase 1 — Determine the version bump
Read the diff since last tag. Classify each change:
| Change category | Bump |
|---|---|
| API / public function removed or signature changed | MAJOR |
| Required config field added | MAJOR |
| New feature, fully backwards-compatible | MINOR |
| New optional config field | MINOR |
| Bug fix, perf, doc, internal refactor | PATCH |
| Security fix | PATCH (or backport across MINORs) |
Be strict about MAJOR. Most teams under-call breaking changes and lose user trust.
Phase 1.5 — Prove the build is green where it actually runs
A local npm test proves the suite passes on your machine. It says nothing
about the other platforms CI covers, and a green local run beside a red badge is
how a project ships eight broken releases in a row without noticing.
gh run list --workflow=CI --limit 5 # is the badge actually green?
gh run view <id> --log-failed # if not, what fails and on which OS?
Never cut a release on a red CI. If the failure is platform-specific, fix or explicitly guard it — do not delete the test, and do not tell the user "all tests passing" when only your platform is passing.
Common one-platform traps:
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.
- 1mo ago Changed · +25 lines a7a3b0f6ea02
- 1mo ago First seen · 202 lines · 71 tokens per session scan A 7b17283d9d79
release-captain is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 12d ago), licensed MIT. It adds 71 tokens to every session and 1,722 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
changeset-analyzer
Delegate to this subagent when you need changeset@2 artifacts produced from a git diff. Input is a git diff, optionally a linked spec@1, and optionally smith's criteriaevidence from the TDD run that produced this diff. A diff spanning multiple independent topics produces one changeset@2 per topic, never one bundled…
release-summarizer
Delegate to this subagent when you need a release-artifact@2 generated from a collection of changeset@2 entries. Input is a list of changeset@2 JSON objects, the prior released version string, and a release date in YYYY-MM-DD format. Each input changeset already carries consumerimpact and semverimpact, set at…
release_chef
Manages versioning, changelog entries, release tags, and identifies breaking changes. Consulted post-cooking when preparing for release.
gamedev-release-manager
You are the Release Manager for an indie game project. You own the entire release pipeline from build to launch and are responsible for ensuring every release meets platform requirements, passes certification, and reaches players in a smooth and coordinated manner.
release-readiness-reviewer
Use when you need to give go/no-go verdicts for demo, handoff, deployment, or release without editing.
release-manager
Expert in release management, semantic versioning, changelogs, and deployment coordination. Use for managing releases, version bumps, and deployment pipelines. Triggers on release, version, changelog, tag, semantic versioning, deploy, ship, publish, npm publish.