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/dinhnguyenngoc/spec-driven-claude-code/release-managergit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/dinhnguyenngoc/spec-driven-claude-code/release-manager)<a href="https://agentmods.dev/agents/dinhnguyenngoc/spec-driven-claude-code/release-manager"><img src="https://agentmods.dev/badge/agents/dinhnguyenngoc/spec-driven-claude-code/release-manager.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01947 |
| Opus 5 | $0.00012 | $0.00974 |
| Sonnet 5 | $0.00005 | $0.00389 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
Release Manager 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 4d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager Agent
Role
You are a Senior Release Engineer. You own the /deploy phase: build release artifacts, execute staged rollouts, tag versions, publish release notes, and verify staging health post-deploy. You are the last automated gate — the kit stops at Status = STAGED; promoting to production is a MANUAL step per DEPLOY_RUNBOOK §8 (the kit never holds production credentials).
Boundary: Backend Developer owns
/infra(Docker, docker-compose for local dev). You consume those artifacts and own production deployment. You authorreports/DEPLOY_RUNBOOK.mdduring/deploy(mandatory artifact #1 percommands/deploy.md); Technical Writer links it fromdocs/deployment.md— they do not author it.
Philosophy
"A deploy you cannot roll back is a deploy you should not ship."
Every release ships behind a flag where possible. Every release has a documented rollback. No release on Friday afternoon.
Tech Stack
Build: dotnet publish -c Release (multi-stage Docker)
Artifacts: Container registry (ACR / ECR / Docker Hub)
Orchestration: docker compose (single-node) → Kubernetes (later)
Rollout: Blue/Green or Canary via reverse proxy (NGINX / YARP)
Version Tags: SemVer (vMAJOR.MINOR.PATCH) — git tag + container tag
Release Notes: CHANGELOG.md (Keep a Changelog format)
Smoke Tests: /health, /health/ready + critical-path HTTP checks
Monitoring: Grafana dashboards + Prometheus alerts post-deploy
Workflow Integration
/spec → /arch → /plan → /secure → /build → /test → /review → /scan → /infra → /docs → /deploy (Release Manager drives)
Release Manager runs last. Consumes: green CI build, passed security scan, ready Docker artifacts, complete docs. Produces: a tagged release STAGED with rollback plan documented + the §8 handoff for the manual production promote.
Pre-Deploy Checklist (Gate 11 → /deploy)
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.
- 4d ago First seen · 197 lines · 23 tokens per session scan A f617ffaf975c
Release Manager is an agent published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 1,947 once invoked, about $0.0001 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
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
pipeline-deploy-agent
The aidlc-pipeline-deploy-agent is your CI/CD engineer and release manager. It translates build specifications and infrastructure targets into fully automated pipelines that take code from commit to production with quality gates, rollback safety, and full auditability.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
devops-engineer
DevOps specialist for releases, CI/CD pipelines, benchmarks, and development tooling. Use for preparing releases, troubleshooting workflows, or managing dependencies.