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.
git clone --depth 1 https://github.com/kadam-official/mcp-serverWrote 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/rules/kadam-official/mcp-server/release-gate)<a href="https://agentmods.dev/rules/kadam-official/mcp-server/release-gate"><img src="https://agentmods.dev/badge/rules/kadam-official/mcp-server/release-gate/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/rules/kadam-official/mcp-server/release-gate"><img src="https://agentmods.dev/badge/rules/kadam-official/mcp-server/release-gate.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.00424 | $0.00424 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
release-gate 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.
What it actually says
Release & Deploy Gate (human-approved)
Merging to main, tagging releases, deploying, and publishing are shared-state,
hard-to-reverse actions. They require an explicit, per-action human "go" — even
when a plan's to-do list names them and even when the agent was told to
"implement the plan / don't stop until all to-dos are done". That instruction
does not override this gate.
The agent MAY do autonomously
- Create branches, commit, push the feature branch.
- Open a GitLab MR (and update its description).
- Run/await CI; run the full local quality gate.
- Report status (e.g. "MR open, pipeline green") and stop.
The agent MUST STOP and get explicit per-action approval before
- Merging an MR into
main(never self-merge; green CI ≠ approval to merge). - Tagging / pushing a release tag (
vX.Y.Z). - Approving the npm-publish gate (this is always a human action).
- Deploying / redeploying any environment — e.g.
rnd.sdev.pw:/root/mcp-kadam,docker compose up, editing a hostdocker-compose.yml. - Force-pushing anything (and never force-push
main/master). - Reverting
mainor deleting release tags (these are also human-gated changes).
Default end state of an autonomous task
"Branch pushed + MR open + CI green", then await the human's instruction for each of the gated steps above. Present the MR link and ask how to proceed; do not chain merge → tag → deploy → publish on your own.
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 · 34 lines · 424 tokens per session scan A 60d45fdb831c
release-gate is a cursor rule published in the GitHub repository kadam-official/mcp-server (0 stars, last pushed 14d ago), licensed MIT. It adds 424 tokens to every session, about $0.0017 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-31.
Other cursor rules, from other repositories
releasing
How to release AdLoop to PyPI — version bumping, tagging, and publishing.
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.
mcp-releasing
Steps and procedures for releasing MCP (Model Context Protocol) servers as NPM packages.
add-to-changelog
Update the project's CHANGELOG.md file with a new entry.
changelog-generator-manual
This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.