agentic-config: Skill for Claude Code

.claude/skills/ac-release/SKILL.md

ac-release is a skill for Claude Code from WaterplanAI/agentic-config. It costs 33 tokens per session (1,402 once invoked), scanned A, original, MIT.

A release checklist that prepares a software version for publication, from a release branch and changelog update through a pull request, tag, and GitHub release.

In plain words
What is it for?
Use it to publish a new version when the project has unreleased changelog entries, including preview releases and optional confirmation skipping.
Why use it?
It keeps required release checks and steps in one workflow, reducing missed version updates or incomplete release records.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is WaterplanAI/agentic-config's own configuration. It tells Claude Code how to work on agentic-config itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-config configures →

Part of the agentic-config plugin — 49 skills, 1 plugin shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to WaterplanAI/agentic-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/WaterplanAI/agentic-config/main/.claude/skills/ac-release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/WaterplanAI/agentic-config

Made for: Claude Code.

Or install agentic-config, the plugin that ships this one along with the rest of its 49 skills, 1 plugin.

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.

agentmods badge for ac-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-release.svg)](https://agentmods.dev/skills/waterplanai/agentic-config/ac-release)
Your own site
<a href="https://agentmods.dev/skills/waterplanai/agentic-config/ac-release"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-release.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,402 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01402
Opus 5 $0.00016 $0.00701
Sonnet 5 $0.00007 $0.00280
Haiku 4.5 $0.00003 $0.00140

Measured 7d ago against content hash d59a4603babc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ac-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 7d 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.

.claude/skills/ac-release/SKILL.md · 230 lines

How it starts

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

Release Skill

Automated release workflow: pre-flight, branch, changelog+version update, PR, merge, tag, GH release.

Arguments

  • --auto — Skip all confirmation gates (pre-flight + PR merge)
  • --preview — Create GH release as prerelease instead of latest

Phase 1: Pre-flight

1.1 Read Current State

CURRENT_VERSION=$(cat VERSION)
# Parse semver: MAJOR.MINOR.PATCH
NEXT_PATCH=$((PATCH + 1))
NEXT_VERSION="$MAJOR.$MINOR.$NEXT_PATCH"
TODAY=$(date +%Y-%m-%d)

Read CHANGELOG.md and extract the ## [Unreleased] section content (everything between ## [Unreleased] and the next ## [ header).

1.2 Validate

  • CHANGELOG [Unreleased] section MUST have content (not empty)
  • If empty: STOP — "No unreleased changes in CHANGELOG.md. Nothing to release."
  • Current branch MUST be main
  • Working tree MUST be clean (git status --porcelain empty)

1.3 Explain Procedure

Display to user:

Release v{NEXT_VERSION}

Current: v{CURRENT_VERSION}
Next:    v{NEXT_VERSION}

Unreleased changes:
{unreleased content summary — first 10 lines}

Procedure:
1. Create branch release/v{NEXT_VERSION}
2. Update CHANGELOG.md and VERSION
3. Create PR, squash-merge to main
4. Tag v{NEXT_VERSION} on main
5. Create GH release ({"prerelease" if --preview else "latest"})

Proceed?

Confirmation gate: Use AskUserQuestion (yes/no). Skip if --auto.

Phase 2: Branch

git checkout -b release/v{NEXT_VERSION}

Phase 3: Update Files

3.1 CHANGELOG.md

Replace the ## [Unreleased] section:

Before:

## [Unreleased]

### Added
- item A
...

After:

## [Unreleased]

## [{NEXT_VERSION}] - {TODAY}

### Added
- item A
...

The [Unreleased] section becomes empty (just the header), and a new versioned section is inserted immediately below it with all the previous unreleased content.

3.2 VERSION

Write {NEXT_VERSION} to VERSION file (single line, no trailing newline beyond what exists).

3.3 Plugin Versions

Update the version field in every plugins/*/.claude-plugin/plugin.json to {NEXT_VERSION}:

Read the full file on GitHub · 230 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.

  1. 7d ago First seen · 230 lines · 33 tokens per session scan A d59a4603babc

Subscribe to this mod's changes

ac-release is a skill published in the GitHub repository WaterplanAI/agentic-config (30 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,402 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-30.

Related

Other skills, from other repositories

share-a-library

Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.

MoizIbnYousaf/Ai-Agent-Skills · 41 tokens

generate-release-notes

Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing.

huytieu/COG-second-brain · 27 tokens

git-flow-pr

Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…

soulcodex/agentic · 103 tokens

git-conventional-commits

Author standardized conventional commit messages (feat, fix, docs, refactor, chore), generate automated semver releases, and format pull request descriptions.

pedroiff0/awesome-skills · 36 tokens

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…

addyosmani/agent-skills · 74 tokens

finishing-a-development-branch

A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.

jnMetaCode/superpowers-zh · 25 tokens