agentmods.dev

nxv: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from utensils/nxv. It costs 13 tokens per session (717 once invoked), scanned A, original, MIT.

A command for reviewing and merging a release-plz release pull request, a proposed set of version and changelog updates.

In plain words
What is it for?
Use it to locate the release pull request, review its version bump and changelog, and safely proceed with a release.
Why use it?
It checks what will be released while requiring explicit confirmation before the merge that publishes the release.

Command for Claude Code

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

This is utensils/nxv's own configuration. It tells Claude Code how to work on nxv 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 nxv configures →

not rated 140repo +1 2mo ago A scan 13 tokens original MIT
View source ↗ utensils/nxv utensils.io
Reuse

Borrowing it

Nothing to install: this file belongs to utensils/nxv. 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/utensils/nxv/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/utensils/nxv

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/nxv/release/github.svg)](https://agentmods.dev/commands/utensils/nxv/release)
Your own site
<a href="https://agentmods.dev/commands/utensils/nxv/release"><img src="https://agentmods.dev/badge/commands/utensils/nxv/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/utensils/nxv/release"><img src="https://agentmods.dev/badge/commands/utensils/nxv/release.svg" alt="Reviewed on agentmods" width="80" 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 717 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.00013 $0.00717
Opus 5.5 $0.00005 $0.00287
Sonnet 5.5 $0.00003 $0.00143
Haiku 4.5 $0.00001 $0.00072

Measured 2mo ago against content hash c6cfa2d0a27f, 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 2mo 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 · 68 lines

How it starts

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

Release

Releases are driven by release-plz (release-plz.toml + .github/workflows/release-plz.yml). On every push to main it maintains a chore: release vX.Y.Z PR with the version bump and CHANGELOG update derived from conventional commits. Merging that PR ships the release — release-plz pushes the vX.Y.Z tag, which triggers release.yml (static binaries, GitHub release, crates.io, Docker) and flakehub-publish-tagged.yml.

This command walks that flow safely. Never merge the release PR without explicit user confirmation — it is an outward-facing, hard-to-reverse action.

Phase 1: Locate the release PR

gh pr list --repo utensils/nxv --search "chore: release in:title" --state open

If none exists, check whether main has unreleased conventional commits since the last tag (git log $(git describe --tags --abbrev=0)..origin/main --oneline). If there are releasable commits but no PR, check the latest Release-plz workflow run for errors (gh run list --workflow release-plz.yml).

Phase 2: Review what will ship

  1. Show the PR's version bump (Cargo.toml diff) and CHANGELOG addition.
  2. Verify the version follows the project convention: feat: commits bump the 0.x minor (features_always_increment_minor = true), fixes bump patch.
  3. If the version or changelog is wrong, edit the release PR directly (it is a normal editable PR) — release-plz preserves manual edits unless new commits land on main.

Phase 3: Pre-flight

  1. All CI checks on the release PR must be green. If checks show "Expected / Waiting", the App token is misconfigured — see release-plz.yml comments.
  2. Confirm no other PR is about to land that should be in this release.

Phase 4: Confirm and merge

Present a summary (version, commit list, changelog) and require the user to confirm with the explicit version number (AskUserQuestion). Then:

gh pr merge <PR> --repo utensils/nxv --squash

Phase 5: Monitor

  1. The Release-plz workflow on main pushes the tag.
  2. The Release workflow builds binaries and publishes — monitor with gh run list --workflow release.yml / gh run watch.
  3. Verify the GitHub release has all four binaries + SHA256SUMS.txt, crates.io has the new version, and ghcr.io has the version tag.

Read the full file on GitHub · 68 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. 2mo ago First seen · 68 lines · 13 tokens per session scan A c6cfa2d0a27f

Subscribe to this mod's changes

release is a command published in the GitHub repository utensils/nxv (140 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 717 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 workflowReleasesclinixnixosnixpkgspackage-manager
Related

release compared with commands from other repositories

release next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releaseutensils/nxvCommand1402mo agoMITA13Claude Code
create-release-note.enfitlab-ai/agent-infraCommand87yesterdayMITA8Claude Code
post-release.enfitlab-ai/agent-infraCommand87yesterdayMITA4Claude Code
release.enfitlab-ai/agent-infraCommand87yesterdayMITA5Claude Code
releaseGoldziher/ai-rulezCommand167yesterdayMITA4Claude Code
shipGoldziher/ai-rulezCommand167yesterdayMITA4Claude Code
mc-publish-addonguguzea/MC-AI-Coding-Assistant-ToolCommand132yesterdaynoneA32Claude Code