release-manager

release-manager is a command for Claude Code from nmime/motiv-buy. It costs 0 tokens per session (2,880 once invoked), scanned A, a copy of release-manager, MIT.

A release-management command for coordinating version changes, tests, documentation, and deployment across multiple packages. It uses GitHub actions and ruv-swarm agents to manage the release process.

In plain words
What is it for?
Use it to prepare releases, create or merge GitHub pull requests, run checks, deploy changes, and document the release.
Why use it?
It brings multi-package release tasks into one workflow and includes validation and rollback steps. This helps avoid releasing related packages out of sync.

Command for Claude Code

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

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is cd ../../ruv-swarm/npm && npm install && npm test:all.

Good fit Use it to prepare releases, create or merge GitHub pull requests, run checks, deploy changes, and document the release.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/nmime/motiv-buy
agentmods
npx agentmods add commands/nmime/motiv-buy/release-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-manager

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/nmime/motiv-buy/release-manager"><img src="https://agentmods.dev/badge/commands/nmime/motiv-buy/release-manager.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 2,880 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 100% 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.02880
Opus 5 $0.00000 $0.01440
Sonnet 5 $0.00000 $0.00576
Haiku 4.5 $0.00000 $0.00288

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

Security

Grade A, and why

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 4d 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

100% identical to release-manager — 82 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 · 356 lines

How it starts

The opening of the file, as written. The whole thing — 356 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 ruv-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__claude-flow__* (all swarm coordination tools)
  • TodoWrite, TodoRead, Task, Bash, Read, Write, Edit

Usage Patterns

1. Coordinated Release Preparation

// Initialize release management swarm
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 6 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Release Coordinator" }
mcp__claude-flow__agent_spawn { type: "tester", name: "QA Engineer" }
mcp__claude-flow__agent_spawn { type: "reviewer", name: "Release Reviewer" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Version Manager" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Deployment Analyst" }

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

// Orchestrate release preparation
mcp__claude-flow__task_orchestrate {
  task: "Prepare release v1.0.72 with comprehensive testing and validation",
  strategy: "sequential",
  priority: "critical"
}

2. Multi-Package Version Coordination

// Update versions across packages
mcp__github__push_files {
  owner: "ruvnet",
  repo: "ruv-FANN",
  branch: "release/v1.0.72",
  files: [
    {
      path: "claude-code-flow/claude-code-flow/package.json",
      content: JSON.stringify({
        name: "claude-flow",
        version: "1.0.72",
        // ... rest of package.json
      }, null, 2)
    },
    {
      path: "ruv-swarm/npm/package.json",
      content: JSON.stringify({
        name: "ruv-swarm",
        version: "1.0.12",
        // ... 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 · 356 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. 4d ago First seen · 356 lines · 0 tokens per session scan A 433111a30efa

Subscribe to this mod's changes

release-manager is a command published in the GitHub repository nmime/motiv-buy (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,880 tokens. A static security scan graded it A with 0 findings. It is 100% identical to release-manager, differing in 82 lines, and is treated as a copy.