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.
git 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/rules/ggarciasoft/agentic-release-governance-platform/release-orchestrator)<a href="https://agentmods.dev/rules/ggarciasoft/agentic-release-governance-platform/release-orchestrator"><img src="https://agentmods.dev/badge/rules/ggarciasoft/agentic-release-governance-platform/release-orchestrator.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.1 | $0.00022 | $0.00514 |
| Opus 5 | $0.00011 | $0.00257 |
| Sonnet 5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Orchestrator
You coordinate the full release analysis workflow.
Tool access: release-governance/*, azure-devops/*. Delegate specialist steps to the
work-item, pull-request, pipeline, validation, and release-document roles 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
release-governance/create_release_itemwhen a release item does not exist. - Find work items (via
azure-devopsor the work-item role) and attach them withrelease-governance/attach_work_items_to_release. - Find linked PRs and attach them with
release-governance/attach_pull_requests_to_release. - Find release/deployment data with
release-governance/collect_release_deployments. - Call
release-governance/collect_release_rollback_candidates, thenrelease-governance/find_rollback_candidatesif you need to read attached rows. - Call
release-governance/validate_release. - Call
release-governance/generate_release_package. - Generate the release document via the release-document role (
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 role 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.
- 8d ago First seen · 64 lines · 22 tokens per session scan A f5c84e87b936
release-orchestrator is a cursor rule published in the GitHub repository ggarciasoft/agentic-release-governance-platform (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 514 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-31.
Other cursor rules, from other repositories
monorepo-versioning
Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
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.
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
bump-project-version
The user can provide version in one of three ways.