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.
npx agentmods add commands/kuadrant/mcp-gateway/releasegit 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.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 | $0.00033 | $0.01879 |
| Opus 5 | $0.00016 | $0.00940 |
| Sonnet 5 | $0.00007 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
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 4d 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 — 206 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.
- 4d ago First seen · 206 lines · 33 tokens per session scan A 8cb4330d78a4
release is a command published in the GitHub repository Kuadrant/mcp-gateway (98 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 1,879 once invoked, about $0.0002 per session on Opus 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.