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 skills add mir-am/skills-agents-ai-coding --skill gh-releasegit clone --depth 1 https://github.com/mir-am/skills-agents-ai-codingWrote 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/mir-am/skills-agents-ai-coding/gh-release)<a href="https://agentmods.dev/skills/mir-am/skills-agents-ai-coding/gh-release"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-release/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/skills/mir-am/skills-agents-ai-coding/gh-release"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-release.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.00021 | $0.04673 |
| Opus 5 | $0.00010 | $0.02337 |
| Sonnet 5 | $0.00004 | $0.00935 |
| Haiku 4.5 | $0.00002 | $0.00467 |
Grade A, and why
gh-release 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 — 563 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Create an annotated git tag for the newest versioned release in
CHANGELOG.md - Create a GitHub prerelease with notes copied from that same changelog entry
- Treat the first versioned section below
## [Unreleased]as the release to publish - Preserve the release section subsections and bullets exactly as written in the changelog
- Preserve the repo's
### Miscsubsection at the end of release notes when present - Append a
## Full Changelogsection that compares the previous release to the new tag - Handle first-release repositories by comparing the default branch's first commit to the new release tag
When to use me
Use this skill when:
- You already ran
changelog-bump-verand now want to publish that version as a git tag and GitHub prerelease - The repository uses
CHANGELOG.mdwith Keep a Changelog style version headings - You want prerelease notes to come directly from the latest versioned changelog section
Do not use this skill when:
CHANGELOG.mdstill only has unreleased notes and no new versioned section yet; runchangelog-bump-verfirst- You want this workflow to rewrite
CHANGELOG.md - You want to publish a full GitHub release instead of a prerelease
Prerequisites
Required:
- Must be a git repository
CHANGELOG.mdexists at the repository rootghis installed and authenticatedoriginremote exists- The working tree is clean
HEADis on the default branchCHANGELOG.mdcontains exactly one## [Unreleased]sectionCHANGELOG.mdcontains at least one versioned release heading below## [Unreleased]
Expected workflow:
- Run
changelog-bump-verfirst so the newest release already exists as a versioned changelog section - Then run
gh-releaseto publish that version as a prerelease
Validation checks:
# Check git repository
git rev-parse --git-dir
# Check changelog exists
[ -f CHANGELOG.md ]
# Check GitHub CLI auth
gh auth status
# Check origin remote exists
git remote get-url origin
# Check working tree is clean
git status --short
# Detect default branch from GitHub metadata
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
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 · 563 lines · 21 tokens per session scan A c19eb03d53ce
gh-release is a skill published in the GitHub repository mir-am/skills-agents-ai-coding (2 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 4,673 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
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release-notes
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
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.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.