A release workflow for preparing a software project and creating an annotated Git tag, a named marker in version history, to start its release process.

Updating versions, writing Keep a Changelog entries, documenting user-facing changes, creating a semantic version tag, and preparing—but not pushing—a release until the user confirms.

It reduces missed release details by checking version numbers, changelog entries, documentation, and tests before publishing.

release — Skill for Claude Code and Codex by jrswab/axe

Install

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.

Any agent

npx skills add jrswab/axe --skill release

Clone the repo

git clone --depth 1 https://github.com/jrswab/axe

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jrswab/axe/release/github.svg)](https://agentmods.dev/skills/jrswab/axe/release)

Your own site

<a href="https://agentmods.dev/skills/jrswab/axe/release"><img src="https://agentmods.dev/badge/skills/jrswab/axe/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jrswab/axe/release"><img src="https://agentmods.dev/badge/skills/jrswab/axe/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,405 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium MCP Rug Pull · line 81
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.

Fix: Pin the image: image:tag or image@sha256:abc123
medium MCP Rug Pull · line 106
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.

Fix: Pin the image: image:tag or image@sha256:abc123

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.01405
Opus 5.5	$0.00012	$0.00562
Sonnet 5.5	$0.00006	$0.00281
Haiku 4.5	$0.00003	$0.00140

Measured 1mo ago against content hash 72f8f6f9a520, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

docs/skills/release/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Your job is to guide the user through a full release for this project. A release includes preparing the code (version bumps, README documentation, changelog), creating an annotated git tag with a v prefix (e.g. v1.5.0), pushing it to trigger the GoReleaser GitHub Actions workflow, setting release notes, and linking the GHCR Docker image.

Rules

Always create an annotated tag (git tag -a), never a lightweight tag.
Tag format is vMAJOR.MINOR.PATCH following Semantic Versioning.
The changelog MUST follow Keep a Changelog 1.1.0 format.
Valid changelog categories: Added, Changed, Deprecated, Removed, Fixed, Security.
All version strings MUST be updated before committing. There are three locations (listed in Reference). Run version tests after bumping to catch drift.
README.md MUST document any user-facing changes — new config fields, CLI flags, behavior changes, exit codes.
DO NOT push to master until the user confirms.
DO NOT push the tag until the user confirms.
DO NOT skip asking the user for the version number, tag annotation message, and changelog review.

Steps

Gather context
- Check the current branch and ensure it is clean (git status).
- List existing tags (git tag --sort=-v:refname) to determine the next version.
- Collect the commit log since the last tag (or all commits if this is the first release).
Ask the user
- What version number to use.
- What the annotated tag message should say.
- Whether the auto-generated changelog looks correct or needs edits.
Categorize commits into Keep a Changelog sections:
- Added — new features and capabilities.
- Changed — changes to existing functionality.
- Deprecated — features marked for removal.
- Removed — features that were removed.
- Fixed — bug fixes.
- Security — vulnerability fixes.
- Exclude commits prefixed with docs:, test:, ci:, or merge commits.

Read the full file on GitHub · 108 lines

Changes

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.

1mo ago First seen · 108 lines · 30 tokens per session scan A 72f8f6f9a520

Subscribe to this mod's changes

release is a skill published in the GitHub repository jrswab/axe (898 stars, last pushed 13d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,405 once invoked, about $0.0001 per session on Opus 5.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-30.

Git and workflow Go Releases ai-agents automation cli command-line developer-tools

release

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Rules

Steps

What this file has done since we first saw it

Other skills, from other repositories

tools-checkout

hotfix-branch

python-format

release-notes

ReleaseNotes

auto-ship