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 rules/ggarciasoft/agentic-release-governance-platform/release-assistantgit 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-assistant)<a href="https://agentmods.dev/rules/ggarciasoft/agentic-release-governance-platform/release-assistant"><img src="https://agentmods.dev/badge/rules/ggarciasoft/agentic-release-governance-platform/release-assistant.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.00640 | $0.00640 |
| Opus 5 | $0.00320 | $0.00320 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
release-assistant 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 5d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Release Assistant — Project Rules
This repository is an MCP-first, agent-host-agnostic release assistant for Azure DevOps. The
same release-governance and azure-devops MCP servers power agents in Cursor, GitHub
Copilot, and Claude. See docs/hosts/agent-hosts-overview.md.
Architecture Principles
- Keep business logic in application services, not in controllers, prompts, or MCP wrappers.
- Keep MCP servers thin: MCP tools delegate to application services.
- Use deterministic validation rules for release readiness.
- Use LLMs only for summarization, document drafting, and guided interaction.
- Treat Azure DevOps data and
release-governanceMCP responses as the source of truth.
Hard Safety Rules
- Never invent work item IDs, PRs, pipeline links, rollback links, statuses, approvals, or dates.
- Mark missing data explicitly as
Missing; never hide it. - Never override or soften MCP validation results.
- Never approve releases, trigger production deployments, or modify Azure DevOps work item states in the MVP.
- Never edit release document Markdown files directly (for example
release.md,release-*.md) or patch document content by hand. Generate and update documents only throughgenerate_release_packageandsave_release_document. To refresh a document, re-run that workflow from the current release package. - Any production-impacting action requires explicit human confirmation and audit logging.
- Never use the API by your own, always try to use MCP availables. If is not possible, ask to the user.
MCP Tools
The release-governance MCP server exposes these canonical tools (see
docs/mcp/mcp-tool-contracts.md):
create_release_item, get_release_item, get_application_mapping,
attach_work_items_to_release, attach_pull_requests_to_release,
attach_deployments_to_release, collect_release_deployments,
find_rollback_candidates, collect_release_rollback_candidates,
attach_rollback_candidates_to_release, validate_release,
generate_release_package, save_release_document.
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.
- 5d ago First seen · 61 lines · 640 tokens per session scan A 6ad3506858ce
release-assistant 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 640 tokens to every session, about $0.0032 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.