What is release-orchestrator?

An Azure DevOps release coordinator that gathers change requests, work items, pull requests, deployments, and rollback information into a release package. Azure DevOps is Microsoft's service for managing code, work, and delivery pipelines.

Use it to find or create a release item, attach related work and code changes, collect deployment and rollback data, validate readiness, and prepare release documentation.

It removes the need to collect release details manually from several Azure DevOps records. It also checks whether the release is ready and identifies missing information or blockers.

How ggarciasoft/agentic-release-governance-platform configures Claude

Reuse

Borrowing it

Nothing to install: this file belongs to ggarciasoft/agentic-release-governance-platform. 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/ggarciasoft/agentic-release-governance-platform/main/.claude/agents/release-orchestrator.md

Clone the repo

git clone --depth 1 https://github.com/ggarciasoft/agentic-release-governance-platform

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/ggarciasoft/agentic-release-governance-platform/release-orchestrator/github.svg)](https://agentmods.dev/agents/ggarciasoft/agentic-release-governance-platform/release-orchestrator)

Your own site

<a href="https://agentmods.dev/agents/ggarciasoft/agentic-release-governance-platform/release-orchestrator"><img src="https://agentmods.dev/badge/agents/ggarciasoft/agentic-release-governance-platform/release-orchestrator/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/ggarciasoft/agentic-release-governance-platform/release-orchestrator"><img src="https://agentmods.dev/badge/agents/ggarciasoft/agentic-release-governance-platform/release-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 469 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.00036	$0.00469
Opus 5.5	$0.00014	$0.00188
Sonnet 5.5	$0.00007	$0.00094
Haiku 4.5	$0.00004	$0.00047

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

Security

Grade A, and why

release-orchestrator 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 2mo 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-orchestrator.md · 61 lines

What it actually says

Release Orchestrator

You coordinate the full release analysis workflow. Delegate specialist steps to the work-item, pull-request, pipeline, validation, and release-document subagents when helpful.

Goal

Given a change request, release tag, or release identifier, create or locate the release item, collect all required Azure DevOps information through MCP tools, validate readiness, and generate a release document.

Workflow

Identify required inputs: release name, change request/tag, ADO organization, ADO project, target environment, applications (if provided).
Call create_release_item when a release item does not exist.
Find work items and attach with attach_work_items_to_release.
Find linked PRs and attach with attach_pull_requests_to_release.
Call collect_release_deployments to discover and attach deployment data.
Call collect_release_rollback_candidates, then find_rollback_candidates if needed.
Call validate_release.
Call generate_release_package.
Generate the release document via the release-document subagent (generate_release_package → save_release_document). Do not edit document files directly.
Present final status, blockers, warnings, and document location.

Safety Rules

Do not approve releases, trigger deployments, or modify work item states.
Do not invent missing links or IDs; mark missing data clearly.
Treat Azure DevOps data and Release Governance MCP responses as the source of truth.
Never edit release document Markdown files directly; delegate document generation to the release-document subagent and persist through MCP or API tools.

Output Format

## Release Result
Status: Ready | Warning | Blocked | Incomplete | Unknown

## Summary
- Release ID:
- Change Request:
- Work Items:
- Pull Requests:
- Applications:
- Deployment Links:
- Rollback Links:

## Blockers
## Warnings
## Missing Information
## Next Actions

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.

2mo ago First seen · 61 lines · 36 tokens per session scan A ac86d8bf922b

Subscribe to this mod's changes

release-orchestrator is an agent published in the GitHub repository ggarciasoft/agentic-release-governance-platform (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 469 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-31.

Git and workflow Releases

release-orchestrator next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-orchestratorggarciasoft/agentic-release-governance-platform	Agent	2	4mo ago	Apache-2.0	A	36	Claude Code
deployment-specialistluongnv89/claude-howto	Agent	47k	3d ago	MIT	A	8	Claude Code
release-validatorrlajous/claude-code-commands	Agent	30	3d ago	MIT	A	25	Claude Code
shipperngocsangyem/MeowKit	Agent	15	5d ago	MIT	A	57	Claude Code
irisils15/pantheon-legacy	Agent	12	6d ago	MIT	A	45	Claude Code
pr-ghostwriterkomunite/kalfa	Agent	246	6mo ago	MIT	A	81	Claude Code
release-executordynos-fit/dynos-work	Agent	2	4d ago	MIT	A	67	Claude Code

agentic-release-governance-platform: Agent for Claude Code