agentmods.dev

release

release is a command for Claude Code from utensils/mcp-nixos. It costs 13 tokens per session (1,091 once invoked), scanned A, original, MIT.

A release procedure for a project that uses Release Please to prepare versions and publish packages. Release Please creates a release pull request from commit messages, and merging it creates the tag and release automatically.

In plain words
What is it for?
Use it to review and merge a release pull request, then check that the resulting PyPI, Docker Hub, GHCR, and FlakeHub artifacts were published from the correct tag.
Why use it?
It prevents mismatched versions, tags, and published files caused by doing release steps by hand. It also clarifies which commit types affect the next release.

Command for Claude Code

not rated 823 +8 today A scan 13 tokens original MIT
View the source file utensils/mcp-nixos
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.

agentmods
npx agentmods add commands/utensils/mcp-nixos/release
Clone the repo
git clone --depth 1 https://github.com/utensils/mcp-nixos

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/utensils/mcp-nixos/release.svg)](https://agentmods.dev/commands/utensils/mcp-nixos/release)
Your own site
<a href="https://agentmods.dev/commands/utensils/mcp-nixos/release"><img src="https://agentmods.dev/badge/commands/utensils/mcp-nixos/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,091 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00013 $0.01091
Opus 5 $0.00006 $0.00545
Sonnet 5 $0.00003 $0.00218
Haiku 4.5 $0.00001 $0.00109

Measured 5d ago against content hash 05168e731145, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release scanned grade A with 1 finding 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 5d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl --fail --silent "https://pypi.org/pypi/mcp-nixos/$VERSION/json" | jq -r .info.version
.claude/commands/release.md · 97 lines

How it starts

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

Release

Releases are managed by Release Please. Do not edit the version, create a tag, or create a GitHub Release by hand during the normal release path.

How it works

  1. Conventional commits merged to main update the open release: vX.Y.Z PR.
  2. The release PR updates pyproject.toml, .release-please-manifest.json, and RELEASE_NOTES.md.
  3. Merging that PR makes Release Please create the matching tag and GitHub Release.
  4. The resulting release.published event runs the existing trusted-publisher workflow, which publishes PyPI, Docker Hub, GHCR, and FlakeHub artifacts from that exact tag.
  5. ci.yml only validates builds; it does not publish rolling container images.

Version rules:

  • fix: produces a patch release.
  • feat: produces a minor release.
  • fix!:, feat!:, or a BREAKING CHANGE: footer produces a major release.
  • Non-user-facing ci:, docs:, test:, refactor:, build:, and chore: commits are hidden and do not cause a release by themselves.

Release checklist

1. Review the release PR

gh pr list --search 'release: in:title is:open' --json number,title,url,headRefName
gh pr view <PR_NUMBER> --json files,commits,reviews,statusCheckRollup
git log "$(git describe --tags --abbrev=0)..origin/main" --oneline

Confirm that:

  • the proposed SemVer bump matches every included change;
  • RELEASE_NOTES.md is complete and calls out breaking changes;
  • pyproject.toml and .release-please-manifest.json contain the same version;
  • CI and review are green.

For the first automated release, verify that the migration merge commit's one-time Release-As: 3.0.0 footer was honored. This major bump is required because Intel macOS flake outputs were removed.

2. Merge the release PR

gh pr merge <PR_NUMBER> --squash --delete-branch

The Release Please workflow owns tag creation and the GitHub Release. Its authenticated release event starts the Publish Package workflow, which owns every publication job. Never create or move the release tag manually.

Read the full file on GitHub · 97 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. 5d ago First seen · 97 lines · 13 tokens per session scan A 05168e731145

Subscribe to this mod's changes

release is a command published in the GitHub repository utensils/mcp-nixos (823 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,091 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflowReleasesai-assistantai-integrationai-toolsanthropicclaudedeveloper-tools
Related

Other commands, from other repositories

release

Prepare and publish a new release of VisionAgent to npm.

sijeeshmiziha/visionagent · 0 tokens

release

Prepare a release by updating docs and bumping the version.

jayminwest/mulch · 1 tokens

release

Generate changelog, bump version, and create git tag.

Joncik91/ucai · 11 tokens

/release

Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.

DataCovey/nornweave · 23 tokens

cut-release

Cut a new arterm release — write the changelog entry, commit it, and tag through quick-release.sh.

Arclude/Arterm-CLI · 22 tokens

imagine

Generate an image from a text description using Grok's /imagine builtin.

LovelaceLoom/grok-plugin-cc · 16 tokens