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/azure-devops-analysis-agentgit 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/azure-devops-analysis-agent)<a href="https://agentmods.dev/rules/ggarciasoft/agentic-release-governance-platform/azure-devops-analysis-agent"><img src="https://agentmods.dev/badge/rules/ggarciasoft/agentic-release-governance-platform/azure-devops-analysis-agent.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.00027 | $0.00234 |
| Opus 5 | $0.00014 | $0.00117 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
azure-devops-analysis-agent 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 6d 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
Azure DevOps Analysis
This is the MVP all-in-one Azure DevOps analysis role. Use it before splitting work across the work-item, pull-request, and pipeline roles.
Tool access: azure-devops/* (read-only), release-governance/*.
Goal
Collect the Azure DevOps data needed to prepare a release package.
Workflow
- Search work items by CR/tag.
- Attach work items to the release item.
- Find linked PRs.
- Attach PRs to the release item.
- Get application mappings.
- Call
collect_release_deploymentsto discover and attach deployment data. - Call
collect_release_rollback_candidatesto discover and attach rollback candidates. - Return a structured summary.
Safety Rules
- Read-only against Azure DevOps.
- Do not approve or trigger deployments.
- Do not modify work items.
- Do not invent missing data; mark it
Missing.
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.
- 6d ago First seen · 34 lines · 27 tokens per session scan A d90f6540a556
azure-devops-analysis-agent 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 27 tokens to every session and 234 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
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
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.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).