Borrowing it
Nothing to install: this file belongs to sanmak/specops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sanmak/specops/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/sanmak/specopsWrote 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.
[](https://agentmods.dev/commands/sanmak/specops/release)<a href="https://agentmods.dev/commands/sanmak/specops/release"><img src="https://agentmods.dev/badge/commands/sanmak/specops/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.
<a href="https://agentmods.dev/commands/sanmak/specops/release"><img src="https://agentmods.dev/badge/commands/sanmak/specops/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01522 |
| Opus 5.5 | $0.00000 | $0.00609 |
| Sonnet 5.5 | $0.00000 | $0.00304 |
| Haiku 4.5 | $0.00000 | $0.00152 |
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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a versioned release: update CHANGELOG, bump version, validate, commit, push, and publish a GitHub Release.
Instructions
Follow these steps precisely. Do NOT add a Co-Authored-By line to the commit.
The version to release is provided via $ARGUMENTS. If $ARGUMENTS is empty or missing, ask the user "What version should this release be? (format: MAJOR.MINOR.PATCH)" and wait for their response before continuing.
Step 1: Validate version
Validate that the version matches semver format MAJOR.MINOR.PATCH (e.g., 1.2.0, 2.0.1). It must NOT have a v prefix -- strip it if present.
If invalid, inform the user and stop.
Step 2: Pre-flight checks
Run all of these checks. If any fail, report the issue and stop.
- Working tree is clean: Run
git status. If there are uncommitted changes, tell the user "Working tree is not clean. Run /commit first or stash changes before releasing." and stop. - On main branch: Run
git rev-parse --abbrev-ref HEAD. If not onmain, tell the user "Releases must be created from the main branch. Currently on<branch>." and stop. - No unpushed commits: Run
git log @{upstream}..HEAD --oneline. If there are unpushed commits, tell the user "There are unpushed commits. Run /push first." and stop. - GitHub CLI available: Run
gh --version. Ifghis not available, tell the user "GitHub CLI (gh) is required for creating releases. Install it with: brew install gh" and stop. - Tag does not exist: Run
git tag -l v<version>. If the tag already exists, tell the user "Tag v already exists. Choose a different version number." and stop.
Step 3: Gather changes since last release
- Find the last release tag:
git describe --tags --abbrev=0 2>/dev/null. If no tags exist, use the root commit. - List all commits since:
git log --oneline <last-tag>..HEAD - Read the full diffs for each commit to understand the actual changes:
git log -p <last-tag>..HEAD - Read the current
CHANGELOG.mdto check if there is existing content in the[Unreleased]section
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 · 136 lines · 0 tokens per session scan A 8cd782dc748d
release is a command published in the GitHub repository sanmak/specops (49 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,522 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.
Other commands, from other repositories
ijfw-ship
Run the IJFW workflow Ship phase (Deep D6). Pre-flight, deploy, and close. Usage: /ijfw-ship.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
release
You are a meticulous release manager. You coordinate releases, maintain changelogs, manage versioning, and ensure every release ships with proper documentation and rollback plans. You have zero tolerance for "just push it to prod" releases.
pr-package
Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…
reqforge-greenkeeper
Diagnose and fix ReqForge repository release gate failures.
release-builder
Build, audit, and publish project to target channel.