What is Release Manager?

An agent that manages the software release and deployment process. It builds release files, rolls changes out in stages, records rollback instructions, and checks staging after deployment.

Use it to build .NET release artifacts, deploy containers through staged rollouts, tag versions, write deployment runbooks and release notes, and verify staging health.

It reduces the risk of releasing a version that cannot be undone or whose deployment problems go unnoticed. Production promotion remains a manual step because the agent does not hold production credentials.

How dinhnguyenngoc/spec-driven-claude-code configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to dinhnguyenngoc/spec-driven-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/dinhnguyenngoc/spec-driven-claude-code/main/.claude/agents/release-manager.md

Clone the repo

git clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-code

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/dinhnguyenngoc/spec-driven-claude-code/release-manager/github.svg)](https://agentmods.dev/agents/dinhnguyenngoc/spec-driven-claude-code/release-manager)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,947 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00023	$0.01947
Opus 5.5	$0.00009	$0.00779
Sonnet 5.5	$0.00005	$0.00389
Haiku 4.5	$0.00002	$0.00195

Measured 1mo ago against content hash f617ffaf975c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/agents/release-manager.md · 197 lines

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 author reports/DEPLOY_RUNBOOK.md during /deploy (mandatory artifact #1 per commands/deploy.md); Technical Writer links it from docs/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)

Read the full file on GitHub · 197 lines

Changes

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 First seen · 197 lines · 23 tokens per session scan A f617ffaf975c

Subscribe to this mod's changes

Release Manager is an agent published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (21 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,947 once invoked, about $0.0001 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.

CI and CD Claude Code DevOps and cloud Git and workflow Releases ai-agents ai-sdlc aspnet-core clean-architecture spec-driven-development

GitHub Actions Node Runtime Upgrade

Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.

github/awesome-copilot · 45 tokens

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…

hyhmrright/brooks-lint · 85 tokens

spec-driven-claude-code: Agent for Claude Code