github:release-manager

github:release-manager is a command for Claude Code from monoes/monomind. It costs 31 tokens per session (2,443 once invoked), scanned A, a copy of release-manager, Apache-2.0.

A tool for coordinating software releases across multiple packages. It supports version changes, testing, pull requests, deployment steps, release documentation, and rollback planning.

In plain words
What is it for?
Use it to prepare and coordinate multi-package releases, validate them, deploy them, and plan rollbacks when needed.
Why use it?
Releases can fail when packages, tests, deployment steps, and documentation are handled separately. This organizes those checks and changes into a coordinated process.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; names the TodoWrite tool; mentions Claude Code.

Good fit Use it to prepare and coordinate multi-package releases, validate them, deploy them, and plan rollbacks when needed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/monoes/monomind/release-manager
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.

Clone the repo
git clone --depth 1 https://github.com/monoes/monomind

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 github:release-manager

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/monoes/monomind/release-manager"><img src="https://agentmods.dev/badge/commands/monoes/monomind/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,443 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 94% 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.00031 $0.02443
Opus 5.5 $0.00012 $0.00977
Sonnet 5.5 $0.00006 $0.00489
Haiku 4.5 $0.00003 $0.00244

Measured yesterday against content hash fc8d24afec1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github:release-manager 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 yesterday.

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

94% identical to release-manager — 195 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/github/release-manager.md · 341 lines

How it starts

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

GitHub Release Manager

Purpose

Automated release coordination and deployment with Monomind swarm orchestration for seamless version management, testing, and deployment across multiple packages.

Capabilities

  • Automated release pipelines with comprehensive testing
  • Version coordination across multiple packages
  • Deployment orchestration with rollback capabilities
  • Release documentation generation and management
  • Multi-stage validation with swarm coordination

Tools Available

  • mcp__github__create_pull_request
  • mcp__github__merge_pull_request
  • mcp__github__create_branch
  • mcp__github__push_files
  • mcp__github__create_issue
  • mcp__monomind__* (all swarm coordination tools)
  • TodoWrite, TodoRead, Task, Bash, Read, Write, Edit

Usage Patterns

1. Coordinated Release Preparation

// Spawn release management agents
mcp__monomind__agent_spawn { type: "coordinator", name: "Release Coordinator" }
mcp__monomind__agent_spawn { type: "tester", name: "QA Engineer" }
mcp__monomind__agent_spawn { type: "reviewer", name: "Release Reviewer" }
mcp__monomind__agent_spawn { type: "coder", name: "Version Manager" }
mcp__monomind__agent_spawn { type: "analyst", name: "Deployment Analyst" }

// Create release preparation branch
mcp__github__create_branch {
  owner: ":owner",
  repo: ":repo",
  branch: "release/v1.0.72",
  from_branch: "main"
}

// Orchestrate release preparation
mcp__monomind__task_create {
  description: "Prepare release v1.0.72 with comprehensive testing and validation",
  agents: ["coordinator", "tester", "reviewer"],
  strategy: "sequential"
}

2. Multi-Package Version Coordination

// Update versions across packages
mcp__github__push_files {
  owner: ":owner",
  repo: ":repo",
  branch: "release/v1.0.72",
  files: [
    {
      path: "packages/@monomind/cli/package.json",
      content: JSON.stringify({
        name: "@monomind/cli",
        version: "1.0.72",
        // ... rest of package.json
      }, null, 2)
    },
    {
      path: "package.json",
      content: JSON.stringify({
        name: "monomind",
        version: "1.0.72",
        // ... rest of package.json
      }, null, 2)
    },
    {
      path: "CHANGELOG.md",
      content: `# Changelog

## [1.0.72] - ${new Date().toISOString().split('T')[0]}

### Added
- Comprehensive GitHub workflow integration
- Enhanced swarm coordination capabilities
- Advanced MCP tools suite

### Changed
- Aligned Node.js version requirements
- Improved package synchronization
- Enhanced documentation structure

### Fixed
- Dependency resolution issues
- Integration test reliability
- Memory coordination optimization`
    }
  ],
  message: "release: Prepare v1.0.72 with GitHub integration and swarm enhancements"
}

Read the full file on GitHub · 341 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. yesterday First seen · 341 lines · 31 tokens per session scan A fc8d24afec1f

Subscribe to this mod's changes

github:release-manager is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 2,443 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to release-manager, differing in 195 lines, and is treated as a copy.