A controlled release command that moves code from the development branch to the main branch, creates a version tag, checks automated publishing, and closes shipped GitHub issues.

Use it to publish a new version after development work is complete. It can verify CI, publish packages and Docker images, create a GitHub release, and close the related issues.

It prevents releases from skipping required checks or using the wrong version. It also keeps the release process and issue updates in one approved path.

How agigante80/actual-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to agigante80/actual-mcp-server. 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/agigante80/actual-mcp-server/main/.claude/commands/release.md

Clone the repo

git clone --depth 1 https://github.com/agigante80/actual-mcp-server

Made for: Claude Code.

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/commands/agigante80/actual-mcp-server/release.svg)](https://agentmods.dev/commands/agigante80/actual-mcp-server/release)

Your own site

<a href="https://agentmods.dev/commands/agigante80/actual-mcp-server/release"><img src="https://agentmods.dev/badge/commands/agigante80/actual-mcp-server/release.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 339 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00339
Opus 5	$0.00000	$0.00169
Sonnet 5	$0.00000	$0.00068
Haiku 4.5	$0.00000	$0.00034

Measured 8d ago against content hash 5190a7fd5e46, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 8d 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/commands/release.md · 19 lines

What it actually says

Release the current develop to main: fast-forward main, tag the new version, confirm the publish pipeline is green, and close the GitHub issues the release shipped. This is the only sanctioned path to main (implement-ticket and merge-pr stop at develop).

Usage

Accepted argument (optional): an expected version (e.g. 0.6.40) to assert against the VERSION on develop as a safety check.

Examples: /release, /release 0.6.40

Steps

Run the release skill (.claude/skills/release/SKILL.md). It:

Verifies the release preconditions (develop ahead of main, version-bumped, develop CI green); stops with a clear next action if any fails, never forcing the release-gate hook.
Computes the release manifest: the version to tag, and the implemented tickets to close (the (#N) references in commit subjects in main..develop, never the CVE/alert numbers in commit bodies).
Fast-forwards main to develop and pushes; waits for the main-push CI run to go green (the same-SHA wait the release-gate hook requires before tagging).
Tags vX.Y.Z and pushes the tag; waits for the release pipeline (npm + multi-arch Docker + Docker Hub + Create Release) to go green.
Closes each implemented ticket that is still open, with a "Released in vX.Y.Z" comment.
Returns to develop and reports the version, the release run conclusion, the published artifacts, and the tickets closed.

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.

8d ago First seen · 19 lines · 0 tokens per session scan A 5190a7fd5e46

Subscribe to this mod's changes

release is a command published in the GitHub repository agigante80/actual-mcp-server (50 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 339 tokens. 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 Releases actual-budget ai-assistant api-server budget-management budget-tracking conversation-ai

actual-mcp-server: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Usage

Steps

What this file has done since we first saw it

Other commands, from other repositories

changelog

finish-branch-execute

opensource

changelog

forge-update

launch