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/steipete/agent-rulesWrote 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/steipete/agent-rules/mcp-releasing)<a href="https://agentmods.dev/rules/steipete/agent-rules/mcp-releasing"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/mcp-releasing/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/steipete/agent-rules/mcp-releasing"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/mcp-releasing.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.01231 |
| Opus 5.5 | $0.00000 | $0.00492 |
| Sonnet 5.5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
mcp-releasing 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-releasing — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing MCP Servers
This document outlines the steps to release a new version of an MCP (Model Context Protocol) server as an NPM package.
Automated Release Preparation
Many MCP projects include an automated release preparation script that performs comprehensive checks before release. Run it with:
npm run prepare-release
This script typically performs the following checks:
- Git Status: Ensures you're on the main branch with no uncommitted changes
- Required Fields: Validates all required fields in package.json
- Dependencies: Checks for missing or outdated dependencies
- Security Audit: Runs npm audit to check for vulnerabilities
- Version Availability: Confirms the version isn't already published
- Version Consistency: Ensures package.json and package-lock.json versions match
- Changelog Entry: Verifies CHANGELOG.md has an entry for the current version
- TypeScript: Compiles and runs tests
- TypeScript Declarations: Verifies .d.ts files are generated
- Native Code (if applicable): Runs format, lint, and tests for Swift/other languages
- Build Verification: Builds everything and verifies the package
- Package Size: Warns if package exceeds reasonable size limits
- MCP Server Smoke Test: Tests the server with a simple JSON-RPC request
If all checks pass, follow the manual steps below.
Manual Pre-Release Steps
-
Update Version Number:
- Decide on the new semantic version number (e.g.,
1.0.0-beta.3,1.0.0,1.1.0). - Update the
versionfield inpackage.json.
- Decide on the new semantic version number (e.g.,
-
Update Documentation:
README.md: Ensure it accurately reflects the latest features, installation instructions, and any breaking changes.- API Documentation: If there are changes to tool schemas or server behavior, update the detailed specification.
- Any other relevant documentation.
-
Update
CHANGELOG.md:- Add a new section for the upcoming release version (e.g.,
## [1.0.0-beta.3] - YYYY-MM-DD). - List all notable changes (Added, Changed, Fixed, Removed, Deprecated, Security) under this version.
- Replace
YYYY-MM-DDwith the current date.
- Add a new section for the upcoming release version (e.g.,
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 · 103 lines · 0 tokens per session scan A ecd1ba4be2ae
mcp-releasing is a cursor rule published in the GitHub repository steipete/agent-rules (5,677 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,231 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 cursor rules, from other repositories
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.
changesets
Writing changesets - when one is needed, apps-only frontmatter, bump levels for deployed apps, summary style, non-interactive creation.
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.
zip-contents-protection.crux
⟦CRUX:zip-contents-protection.md P.⊛{¬auto-Δ scripts/create-crux-zip.py w/o user req!}.
version-bump.crux
⟦CRUX:version-bump.md Κ{M=X.0.0;m=0.X.0;p=0.0.X} R{fix|docs|style|refactor|perf|test|chore→p;feat→m;BREAKING|!→M} Λ{⊲commit→Δ.crux/crux.json»stage} P{1bump;↑→↓0;¬conv→?} ⟧.
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.