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.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/instructions/ggarciasoft/agentic-release-governance-platform/claude-md)<a href="https://agentmods.dev/instructions/ggarciasoft/agentic-release-governance-platform/claude-md"><img src="https://agentmods.dev/badge/instructions/ggarciasoft/agentic-release-governance-platform/claude-md/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/instructions/ggarciasoft/agentic-release-governance-platform/claude-md"><img src="https://agentmods.dev/badge/instructions/ggarciasoft/agentic-release-governance-platform/claude-md.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.00621 | $0.00621 |
| Opus 5 | $0.00311 | $0.00311 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
agentic-release-governance-platform CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project memory and instructions for Claude Code working in this repository.
This is an MCP-first, agent-host-agnostic release assistant for Azure DevOps. The same
release-governance and azure-devops MCP servers power agents in Claude, Cursor, and GitHub
Copilot. See docs/hosts/agent-hosts-overview.md.
Subagents
Role-specific subagents live in .claude/agents/. Claude can delegate to them automatically
based on each subagent's description, or you can invoke them explicitly (for example,
"use the release-orchestrator subagent ..."). The four MVP roles are release-orchestrator,
azure-devops-analysis-agent, validation-agent, and release-document-agent.
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.
Use the azure-devops MCP server (read-only) for raw work items, PRs, and pipeline data.
Hard Safety Rules
- Treat Azure DevOps data and
release-governanceMCP responses as the source of truth. - 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(or the equivalent API document endpoints). To refresh a document, re-run that workflow from the current release package. - Any production-impacting action requires explicit human confirmation and audit logging.
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 · 58 lines · 621 tokens per session scan A 120049f6e7b5
agentic-release-governance-platform CLAUDE.md is an instructions file published in the GitHub repository ggarciasoft/agentic-release-governance-platform (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 621 tokens to every session, about $0.0031 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 instructions, from other repositories
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.