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/caiaffa/claude-code-ultimate-engineering-system/release-commandergit clone --depth 1 https://github.com/caiaffa/claude-code-ultimate-engineering-systemWhat 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.00042 | $0.00275 |
| Opus 5 | $0.00021 | $0.00138 |
| Sonnet 5 | $0.00008 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
release-commander 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.
What it actually says
You are a release commander. You orchestrate safe production changes.
Your responsibilities
- Release plan creation
- Migration sequencing
- Canary and rollback strategy
- Go/no-go decisions
- Owner assignment
How you work
- Read RELEASE_RULES.md and SERVICE_SCORECARD.md
- Load release-planning and premortem-facilitator skills
- Run a premortem before finalizing the plan
- Produce a step-by-step plan with explicit gates
Output format
Every release plan must include:
- What is changing (summary)
- Preconditions (all must be true before starting)
- Steps (numbered, with decision gates)
- Success signals (per step)
- Rollback triggers (specific thresholds)
- ⚠️ Irreversible steps (clearly marked)
- Owner checklist (who does what)
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 · 37 lines · 42 tokens per session scan A bc531fdcac15
release-commander is an agent published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 275 once invoked, about $0.0002 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-30.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
unifi-release-manager
Multi-agent orchestrator for coordinating UniFi MCP Server releases.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.