Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
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.
git clone --depth 1 https://github.com/ruvnet/ruflonpx agentmods add commands/ruvnet/ruflo/release-managerWrote 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.
[](https://agentmods.dev/commands/ruvnet/ruflo/release-manager)<a href="https://agentmods.dev/commands/ruvnet/ruflo/release-manager"><img src="https://agentmods.dev/badge/commands/ruvnet/ruflo/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.
<a href="https://agentmods.dev/commands/ruvnet/ruflo/release-manager"><img src="https://agentmods.dev/badge/commands/ruvnet/ruflo/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02894 |
| Opus 5.5 | $0.00000 | $0.01158 |
| Sonnet 5.5 | $0.00000 | $0.00579 |
| Haiku 4.5 | $0.00000 | $0.00289 |
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 1mo 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.
This is a copy
100% identical to release-manager — 4 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.
How it starts
The opening of the file, as written. The whole thing — 338 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_requestmcp__github__merge_pull_requestmcp__github__create_branchmcp__github__push_filesmcp__github__create_issuemcp__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"
}
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.
- 1mo ago First seen · 338 lines · 0 tokens per session scan A 39c2907d2518
release-manager is a command published in the GitHub repository ruvnet/ruflo (77,829 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,894 tokens. A static security scan graded it A with 0 findings. It is 100% identical to release-manager, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
release
(dev-only) release maintainer harness — MoAI-ADK production release (git-flow: rc build on develop, release/vX.Y.Z cut from develop, PR to main, scripts/release.sh + GoReleaser, back-merge into develop). NOT distributed to user projects.
factory-ship
Release — open a develop → master PR, wait for CI, merge, verify the deploy.
sync-ecosystem
Detect API changes, sync satellite repos, and publish releases.
changelog
Auto-generate release notes from merged PRs and FORGE:TRAJECTORY annotations — grouped by conventional commit type.
work-flow-release
Complete workflow to prepare and publish a release.