mcp-server-manager: Skill for Claude Code

.agents/skills/release-mcpsm/SKILL.md

release-mcpsm is a skill for Claude Code from sardine-ai/mcp-server-manager. It costs 28 tokens per session (1,199 once invoked), scanned A, original, MIT.

A release workflow for mcp-server-manager, a project that manages MCP servers. It creates a GitHub release using semantic versioning, where major, minor, and patch describe the size of a change.

In plain words
What is it for?
Use it to prepare major, minor, or patch releases, generate notes from merged pull requests, and create the GitHub release that starts the publishing workflow.
Why use it?
It checks that the repository is on the main branch and clean before releasing, then leaves version updates and npm publishing to CI, the automated build system.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is sardine-ai/mcp-server-manager's own configuration. It tells Claude Code how to work on mcp-server-manager itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-server-manager configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sardine-ai/mcp-server-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sardine-ai/mcp-server-manager/main/.agents/skills/release-mcpsm/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sardine-ai/mcp-server-manager

Made for: Claude Code.

Wrote 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.

agentmods badge for release-mcpsm

README.md
[![agentmods](https://agentmods.dev/badge/skills/sardine-ai/mcp-server-manager/release-mcpsm/github.svg)](https://agentmods.dev/skills/sardine-ai/mcp-server-manager/release-mcpsm)
Your own site
<a href="https://agentmods.dev/skills/sardine-ai/mcp-server-manager/release-mcpsm"><img src="https://agentmods.dev/badge/skills/sardine-ai/mcp-server-manager/release-mcpsm/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.

agentmods 80×15 button for release-mcpsm

Your own site · 80×15
<a href="https://agentmods.dev/skills/sardine-ai/mcp-server-manager/release-mcpsm"><img src="https://agentmods.dev/badge/skills/sardine-ai/mcp-server-manager/release-mcpsm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,199 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.01199
Opus 5 $0.00014 $0.00600
Sonnet 5 $0.00006 $0.00240
Haiku 4.5 $0.00003 $0.00120

Measured 10d ago against content hash dc674d93cf5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

release-mcpsm 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 10d 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.

.agents/skills/release-mcpsm/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release mcp-server-manager

Create a new release following semantic versioning. This workflow will:

  1. Verify repository state (on main, clean working directory)
  2. Calculate the new version
  3. Generate release notes from merged PRs
  4. Create GitHub release (which triggers CI to bump package.json and publish to npm)

Important: The CI workflow (.github/workflows/publish.yml) automatically handles:

  • Updating package.json version
  • Committing the version bump to main
  • Publishing to npm

You only need to create the GitHub release — everything else is automated.

Prerequisites Check

Before starting, verify:

# Must be on main branch
git branch --show-current  # Should output: main

# Working directory must be clean
git status --porcelain  # Should be empty

# Pull latest changes
git pull origin main

If not on main or working directory is dirty, STOP and report the issue.

Version Bump Type

The release type is specified via $ARGUMENTS:

  • major: Breaking changes (1.0.0 -> 2.0.0)
  • minor: New features (1.0.0 -> 1.1.0)
  • patch: Bug fixes (1.0.0 -> 1.0.1)

If $ARGUMENTS is empty, ask the user which type of release to create.

Release Process

Step 1: Get Current Version

Read package.json to get the current version:

node -p "require('./package.json').version"

Step 2: Calculate New Version

Based on current version and bump type ($ARGUMENTS), calculate the new version:

  • For major: Increment first number, reset others to 0
  • For minor: Increment second number, reset patch to 0
  • For patch: Increment third number

Example: Current is 2.2.11

  • major -> 3.0.0
  • minor -> 2.3.0
  • patch -> 2.2.12

Step 3: Get Latest Tag and PRs

# Get latest tag
git describe --tags --abbrev=0

# Get merged PRs since last tag (replace <last-tag> with actual tag)
git log <last-tag>..HEAD --merges --oneline

Parse the merge commits to extract PR numbers and titles:

  • Format: Merge pull request #<number> from <branch>
  • Extract the PR number and title

Read the full file on GitHub · 186 lines

Changes

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.

  1. 10d ago First seen · 186 lines · 28 tokens per session scan A dc674d93cf5a

Subscribe to this mod's changes

release-mcpsm is a skill published in the GitHub repository sardine-ai/mcp-server-manager (8 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,199 once invoked, about $0.0001 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-31.