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/github-release-incident-flownpx skills add chf3198/copilot-governance --skill github-release-incident-flowgit 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/github-release-incident-flow)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/github-release-incident-flow"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/github-release-incident-flow.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.00029 | $0.00260 |
| Opus 5 | $0.00015 | $0.00130 |
| Sonnet 5 | $0.00006 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
github-release-incident-flow 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
GitHub Release Incident Flow
Purpose
Standardize release and incident lifecycle controls in GitHub Issues/PRs/Projects.
Core checks
- Release notes/changelog readiness
- Validation evidence linked to release item
- Rollback path and owner documented
- Incident severity/impact/owner/containment recorded
- Hotfix branch+PR linkage to incident
- Follow-up prevention tickets created before closure
Output format
RELEASE_INCIDENT_REPORT
mode: <release-readiness|incident-flow|post-incident>
scope: <repo|org>
policy_profile: <strict|standard|light>
findings:
- <check status + evidence>
actions:
1) <action + owner + verification>
decision:
- <apply|defer|NO_CHANGE>
missing_evidence:
- <none or artifacts>
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 · 40 lines · 29 tokens per session scan A a766f4845729
github-release-incident-flow is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 260 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 skills, from other repositories
repo-recap
Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass "en" or "fr" as argument for language (default fr).
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gh-axi
Operate GitHub through the gh-axi CLI - issues, pull requests, workflow runs, workflows, releases, repositories, labels, Projects (v2), Actions secrets and variables, search, and raw API access. Use whenever a task touches GitHub: listing or filing issues, reviewing or merging PRs, checking CI runs, triggering…
gsd-complete-milestone
Archive completed milestone and prepare for next version.
github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.