agentmods.dev

release

A release command that prepares and publishes a new version of a software project on GitHub.

In plain words
What is it for?
Use it to determine a major, minor, or patch version from recent commits, run checks, update package versions, create a Git tag, push changes, and publish a GitHub release.
Why use it?
It removes the manual work of choosing a version number, checking the project, updating version files, and creating the release. It stops when the working tree, branch, lint checks, or tests are not ready.

Command for Claude Code

11 1mo ago A scan 0 tokens original MIT
View the source file Sealjay/mcp-hey
Install

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.

agentmods
npx agentmods add commands/sealjay/mcp-hey/release
Clone the repo
git clone --depth 1 https://github.com/Sealjay/mcp-hey

Made for: Claude Code.

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 393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00393
Opus 5 $0.00000 $0.00197
Sonnet 5 $0.00000 $0.00079
Haiku 4.5 $0.00000 $0.00039

Measured 3d ago against content hash 8e8e23dfa519, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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

Copies of this mod

1 near-identical copy found in the catalogue:

  • release — 89% identical, 9 lines differ
.claude/commands/release.md · 33 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
    • bun run lint must pass
    • bun test must pass

  4. Version bump: update the version field in both package.json and src/index.ts (the version string in the Server constructor), 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. 3d ago First seen · 33 lines · 0 tokens per session scan A 8e8e23dfa519

Subscribe to this mod's changes

release is a command published in the GitHub repository Sealjay/mcp-hey (11 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 393 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.

Git and workflowReleasesai-agentsemailhey-emailmcpmodel-context-protocol
Related

Other commands, from other repositories

release

Create a new Remarc release using the automated GitHub Actions workflow.

metedata/Remarc · 0 tokens

/release

Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.

DataCovey/nornweave · 23 tokens

deploy-prod

Create a production deployment PR from main to deploy/prod with auto-versioning.

WaniWani-AI/sdk · 15 tokens

release

Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.

capazme/mcp-legal-it · 56 tokens

changelog

Generate a changelog summary for a Linear project and copy to clipboard.

WaniWani-AI/sdk · 13 tokens

release

Comprehensive workflow for releasing a new version of the VectorMCP Ruby gem following best practices.

sergiobayona/vector_mcp · 0 tokens