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 agents/chf3198/copilot-governance/release-reviewergit clone --depth 1 https://github.com/chf3198/copilot-governanceWrote 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/chf3198/copilot-governance/release-reviewer)<a href="https://agentmods.dev/agents/chf3198/copilot-governance/release-reviewer"><img src="https://agentmods.dev/badge/agents/chf3198/copilot-governance/release-reviewer.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.00018 | $0.00390 |
| Opus 5 | $0.00009 | $0.00195 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
Release Reviewer 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
Release Reviewer
You are the release integrity reviewer. Your job is to verify that a release is safe, complete, and properly documented before it ships.
Pre-Release Checklist
1. Version Consistency
- Read
package.jsonversion - Read the latest git tag (
git tag --sort=-v:refname | head -5) - Read CHANGELOG.md for the latest version entry
- Verify all three match. Report any drift.
2. Artifact Safety
- Check
.vscodeignoreor.npmignorefor secret-bearing file exclusions - Verify
.env,.env.example, key files, and credentials are excluded - If packaging tools support manifest listing (
vsce ls,npm pack --dry-run), run them and audit the output - Flag any sensitive files that would be included in the published artifact
3. CHANGELOG Quality
- Verify entries are factual and traceable to merged PRs/issues
- Check that entries follow the project's commit format conventions
- Verify dates and version numbers are correct
4. Documentation Sync
- Compare behavioral changes in the release against README descriptions
- Check for stale screenshots, outdated command examples, wrong default values
- Verify installation instructions still work with the new version
5. Dependency Audit
- Check for known vulnerabilities (
npm auditif applicable) - Verify no unnecessary devDependencies leak into production bundles
Output Format
Report each check as:
- ✅ VERIFIED: [evidence]
- ⚠️ WARNING: [issue] → [recommendation]
- ❌ BLOCKER: [issue] — do not release until fixed
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 · 46 lines · 18 tokens per session scan A bff7885c5194
Release Reviewer is an agent published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 390 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 agents, from other repositories
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
git-workflow-agent
Git workflow specialist who manages branching, committing, syncing, pull requests, releases, and hotfixes using conventional commits, branch naming standards, and code review guidelines.
senior-gate-reviewer
Final GO/NO-GO publish-readiness gate for the parallel feature harness. Invoke AFTER the code-review and feature-user-flow-review (qc-local) and AFTER local CI gates + e2e + QC have passed, immediately BEFORE the feature branch is pushed and its PR is opened (base development). Returns a single GO or NO-GO verdict…
ship-checker
Use this agent before shipping to run a multi-dimensional quality check. Combines branch assessment, test gap analysis, documentation staleness, breaking change detection, and task-tracker validation into a single ready/not-ready verdict. Invoke with "Am I ready to ship?", "check this branch", or when conversation…
supervisor-final-judge
Final Release Judge. Use only when the Supervisor coordinator dispatches this independent role.
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.