Borrowing it
Nothing to install: this file belongs to nanotaboada/go-samples-gin-restful. 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/nanotaboada/go-samples-gin-restful/master/.claude/commands/pre-release.mdgit clone --depth 1 https://github.com/nanotaboada/go-samples-gin-restfulWrote 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/nanotaboada/go-samples-gin-restful/pre-release)<a href="https://agentmods.dev/commands/nanotaboada/go-samples-gin-restful/pre-release"><img src="https://agentmods.dev/badge/commands/nanotaboada/go-samples-gin-restful/pre-release.svg" alt="Measured on agentmods" 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.01402 |
| Opus 5 | $0.00000 | $0.00701 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
pre-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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the pre-release checklist for this project. Work through all three phases in order, pausing for explicit confirmation at each decision point before proceeding. Never create a branch, commit, tag, or push without approval.
Phase 1 — Determine next release
-
Run
git statusand confirm the working tree is clean and onmaster. If not, stop and report the problem. -
Run
git tag --sort=-v:refnameto list existing tags. Identify the most recent tag matchingv*.*.*-*and extract its player codename. -
Read the A–Z player table from
CHANGELOG.mdto find the next player:- No tags yet: start at
A(first player in the table). - Normal case: use the player that follows the last used codename alphabetically. If letters were skipped, pick the next after the highest existing codename — do not backfill gaps.
- Last codename is
Z(Zico): the list is finite. Stop and flag that the naming convention needs to be revisited before proceeding.
- No tags yet: start at
-
Read the
[Unreleased]section ofCHANGELOG.mdand infer the version bump using these rules (applied in order — first match wins):- Any entry contains the word BREAKING (case-insensitive), a
BREAKING CHANGE:token in a commit footer, or a!suffix after the commit type/scope (e.g.feat!:orfeat(scope)!:) → major bump - Any
### Addedentry introduces a new endpoint, request parameter, or client-visible API response → minor bump. Test additions, documentation (ADRs, README, Swagger regen), and internal tooling do not qualify. - Otherwise (only
### Changed,### Fixed,### Removed, or non-API additions) → patch bump
- Any entry contains the word BREAKING (case-insensitive), a
-
Compute the next version by applying the bump to the current latest tag's semver (e.g.
v2.0.0-bobby+ minor →2.1.0). -
Present a summary for confirmation before continuing:
- Last tag and player
- Next version and player codename
- Bump type and the reasoning (what triggered it)
- Proposed tag:
vX.Y.Z-{player} - Proposed branch:
release/vX.Y.Z-{player}
Wait for explicit approval before proceeding to Phase 2.
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.
- 7d ago First seen · 126 lines · 0 tokens per session scan A 9effcf1ee493
pre-release is a command published in the GitHub repository nanotaboada/go-samples-gin-restful (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,402 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-31.
Other commands, from other repositories
resolve-conflicts
/ai-sdlc resolve-conflicts — manually invoke the ci-conflict-resolver agent against a single PR. Phase 1 surface (AISDLC-460) for the same agent the ci-failure-watcher dispatches automatically. Use when CI failed on a stale base and you'd like the rebase + re-arm to happen now rather than waiting for the next watcher…
cleanup
Remove worktrees under .worktrees/ — defaults to merged-PR sweep, or pass a task-id to force-remove a specific one.
align
Context-aware alignment. When in plan mode, it reviews the active plan. Otherwise, it reviews all branch changes against Ion quality gates and principles, implements the fixes and commits them after operator approval.
create-issue
Open a GitHub issue on the Ion engine repo for a bug or feature request derived from the current conversation, with consumer project details scrubbed.
squash
Rebuild a feature branch into clean conventional commits while preserving its exact final tracked tree.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.