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 skills/chf3198/copilot-governance/release-version-integritynpx skills add chf3198/copilot-governance --skill release-version-integritygit 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/skills/chf3198/copilot-governance/release-version-integrity)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/release-version-integrity"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/release-version-integrity.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 | $0.00038 | $0.00410 |
| Opus 5 | $0.00019 | $0.00205 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
release-version-integrity 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 4d 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 Version Integrity
When to use
- Before any release or publish action.
- When
package.json/manifest version, git tag, and changelog may be inconsistent. - After cherry-picks or hotfixes that bypassed normal release flow.
Procedure
- Detect release source-of-truth files (manifest + changelog + workflow triggers).
- Compare tag version, manifest version, and changelog head version.
- Determine the canonical install channel and whether exact-version install/pinning is supported.
- Check publish workflow for explicit version/tag validation gates.
- Confirm artifact preflight exists (
vsce ls/equivalent package manifest audit). - Require a post-publish availability gate for exact-version installability when platform supports it.
- Verify update notifications and release announcements use the same canonical version source as installers.
- Propose the smallest change that makes drift structurally unlikely.
Output format
integrity_status: pass|faildrift_points: exact mismatches foundversion_selectability: supported|not-supported|unknownselectability_status: pass|fail|n/arequired_gates: missing required checksminimal_fix_plan: ordered steps to remediateevidence: files and checks reviewed
Standards
- Do not claim release readiness without explicit evidence.
- Prefer automated versioning flows over manual multi-file updates.
- Keep release metadata factual and traceable.
- For platforms supporting exact-version install/pinning, do not mark readiness unless exact-version installability is verified post-publish.
- Require immutable release artifacts and documented retention/yank policy for versioned channels.
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.
- 4d ago First seen · 45 lines · 38 tokens per session scan A 9d088084b0b1
release-version-integrity is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 410 once invoked, about $0.0002 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.