Borrowing it
Nothing to install: this file belongs to Kuadrant/mcp-gateway. 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/Kuadrant/mcp-gateway/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/Kuadrant/mcp-gatewayWrote 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/kuadrant/mcp-gateway/release)<a href="https://agentmods.dev/commands/kuadrant/mcp-gateway/release"><img src="https://agentmods.dev/badge/commands/kuadrant/mcp-gateway/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/kuadrant/mcp-gateway/release"><img src="https://agentmods.dev/badge/commands/kuadrant/mcp-gateway/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.00033 | $0.01777 |
| Opus 5.5 | $0.00013 | $0.00711 |
| Sonnet 5.5 | $0.00007 | $0.00355 |
| Haiku 4.5 | $0.00003 | $0.00178 |
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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a release of mcp-gateway. Argument is the target version (e.g., 0.6.0, 0.7.0-rc1).
Version: $ARGUMENTS
If no version argument was provided, ask the user for it.
Determine release type
Parse the version to determine:
- RC release: version contains
-rcsuffix (e.g.,0.6.0-rc1) - Final release: no suffix (e.g.,
0.6.0) - Patch release: patch > 0 and no suffix (e.g.,
0.6.1)
Extract the major.minor for the release branch name (release-X.Y).
Remote layout
This repo uses a fork workflow. Confirm with git remote -v:
origin= user's fork (e.g.,<your-fork>/mcp-gateway)upstream= Kuadrant/mcp-gateway
Both main and release-* branches have branch protection -- all changes require PRs.
Important notes
- All changes go through PRs -- never push directly to protected branches
- The
set-release-version.shscript handles all version string updates across docs, scripts, and manifests - Creating the GitHub release triggers CI workflows that build images and push the Helm chart
- Workflow URLs to watch:
Safety rules
Follow these throughout the entire process:
- Never push to any remote. Always tell the user what to push and let them do it.
- Never create PRs or issues. Provide the exact
gh pr createcommand for the user to run. - Never create GitHub releases. Walk the user through it.
- Check for uncommitted changes before any
git checkout. If the working tree is dirty, stop and ask the user how to proceed. - Show diffs and ask for confirmation before committing. Never commit without the user confirming the changes look correct.
- Never use
git add .orgit add -A. Only stage specific paths relevant to the version bump.
Steps
1. Pre-flight checks
Before doing anything:
- Run
git statusto check for uncommitted changes. If dirty, stop and ask the user. - Run
git remote -vto confirm the remote layout matches expectations. - Confirm the target version with the user before proceeding.
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 Changed · +1 lines 3a5586e278d1
- 2mo ago First seen · 206 lines · 33 tokens per session scan A 8cb4330d78a4
release is a command published in the GitHub repository Kuadrant/mcp-gateway (108 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 1,777 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.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.