mcp-signal: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from Sealjay/mcp-signal. It costs 0 tokens per session (413 once invoked), scanned A, a copy of release, MIT.

A command that releases a new software version by choosing the version change, running checks, updating files, tagging the code, and creating a GitHub release.

In plain words
What is it for?
Use it to publish major, minor, or patch releases after commits are reviewed and tests and lint checks pass.
Why use it?
It turns a release checklist into a repeatable process and stops when the repository is not ready.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is Sealjay/mcp-signal's own configuration. It tells Claude Code how to work on mcp-signal 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-signal configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Sealjay/mcp-signal. 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/Sealjay/mcp-signal/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/Sealjay/mcp-signal

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/sealjay/mcp-signal/release/github.svg)](https://agentmods.dev/commands/sealjay/mcp-signal/release)
Your own site
<a href="https://agentmods.dev/commands/sealjay/mcp-signal/release"><img src="https://agentmods.dev/badge/commands/sealjay/mcp-signal/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/sealjay/mcp-signal/release"><img src="https://agentmods.dev/badge/commands/sealjay/mcp-signal/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 413 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.
Origin 89% copy Near-identical to another mod 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.00000 $0.00413
Opus 5.5 $0.00000 $0.00165
Sonnet 5.5 $0.00000 $0.00083
Haiku 4.5 $0.00000 $0.00041

Measured 2mo ago against content hash 33aaae0856d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

Origin

This is a copy

89% identical to release — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/release.md · 34 lines

What it actually says

Release a new version. Determines the bump type from recent commits, runs the full checklist, tags, pushes, and creates a GitHub release.

Steps

  1. Determine bump type from commits since the last tag:

    • If $ARGUMENTS is major, minor, or patch, use that directly.
    • Otherwise, inspect git log $(git describe --tags --abbrev=0)..HEAD --oneline:
      • Any commit mentioning "breaking" or "BREAKING CHANGE" -> major
      • Any commit with feat: prefix or new tool registrations -> minor
      • Otherwise -> patch
  2. Calculate next version: parse the latest tag (git describe --tags --abbrev=0), increment the appropriate component, reset lower components to 0.

  3. Pre-flight checks (abort on failure):

    • git status must show a clean working tree (no uncommitted changes)
    • git branch --show-current must be main
    • uv run ruff check . must pass
    • uv run pytest must pass
  4. Version bump: update the version string in both pyproject.toml (the version field under [project]) and src/mcp_signal/server.py (the version= argument to FastMCP), then commit with message chore: bump version to <MAJOR>.<MINOR>.<PATCH>.

  5. Tag and release:

    • git tag v<MAJOR>.<MINOR>.<PATCH>
    • git push origin main
    • git push origin v<MAJOR>.<MINOR>.<PATCH>
    • gh release create v<MAJOR>.<MINOR>.<PATCH> --generate-notes
  6. Report: print the new version, release URL, and a one-line summary.

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. 2mo ago First seen · 34 lines · 0 tokens per session scan A 33aaae0856d5

Subscribe to this mod's changes

release is a command published in the GitHub repository Sealjay/mcp-signal (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 413 tokens. A static security scan graded it A with 0 findings. It is 89% identical to release, differing in 9 lines, and is treated as a copy.

Related

release compared with commands from other repositories

release next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releaseSealjay/mcp-signalCommand02d agoMITA0Claude Code
landgmickel/flow-nextCommand717yesterdayMITA13Claude Code
qualityDesko77/claude-code-skills-1cCommand90yesterdayMITA18Claude Code
release-notesOpenHands/extensionsCommand176yesterdayMITA44Claude Code
release-managerruvnet/agentic-flowCommand838yesterdaynoneA0Claude Code
create-prdsswift/ionCommand52d agoMITA28Claude Code
rally-merge-prddgonzal3/rallyCommand63d agoMITA0Claude Code