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.
curl -O https://raw.githubusercontent.com/ggarciasoft/agentic-release-governance-platform/main/.claude/agents/release-orchestrator.mdgit clone --depth 1 https://github.com/ggarciasoft/agentic-release-governance-platformWrote 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/ggarciasoft/agentic-release-governance-platform/release-orchestrator)<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.
<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>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 | $0.00018 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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 9d 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
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_itemwhen 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_deploymentsto discover and attach deployment data. - Call
collect_release_rollback_candidates, thenfind_rollback_candidatesif 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
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.
- 9d ago First seen · 61 lines · 36 tokens per session scan A ac86d8bf922b
release-orchestrator is an agent published in the GitHub repository ggarciasoft/agentic-release-governance-platform (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 469 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-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
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.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.