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/akhilyad/deployynpx agentmods add skills/akhilyad/deployy/agent-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/skills/akhilyad/deployy/agent-release-manager)<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-release-manager"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-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/skills/akhilyad/deployy/agent-release-manager"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-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.00016 | $0.03133 |
| Opus 5.5 | $0.00006 | $0.01253 |
| Sonnet 5.5 | $0.00003 | $0.00627 |
| Haiku 4.5 | $0.00002 | $0.00313 |
Grade A, and why
agent-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 14d 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
95% identical to agent-release-manager — 46 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: release-manager description: Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages type: development color: "#FF6B35" tools:
- Bash
- Read
- Write
- Edit
- TodoWrite
- TodoRead
- Task
- WebFetch
- mcp__github__create_pull_request
- mcp__github__merge_pull_request
- mcp__github__create_branch
- mcp__github__push_files
- mcp__github__create_issue
- mcp__hyrex__swarm_init
- mcp__hyrex__agent_spawn
- mcp__hyrex__task_orchestrate
- mcp__hyrex__memory_usage hooks: pre_task: | echo "🚀 Initializing release management pipeline..." npx ruv-swarm hook pre-task --mode release-manager post_edit: | echo "📝 Validating release changes and updating documentation..." npx ruv-swarm hook post-edit --mode release-manager --validate-release post_task: | echo "✅ Release management task completed. Updating release status..." npx ruv-swarm hook post-task --mode release-manager --update-status notification: | echo "📢 Sending release notifications to stakeholders..." npx ruv-swarm hook notification --mode release-manager
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
Usage Patterns
1. Coordinated Release Preparation
// Initialize release management swarm
mcp__hyrex__swarm_init { topology: "hierarchical", maxAgents: 6 }
mcp__hyrex__agent_spawn { type: "coordinator", name: "Release Coordinator" }
mcp__hyrex__agent_spawn { type: "tester", name: "QA Engineer" }
mcp__hyrex__agent_spawn { type: "reviewer", name: "Release Reviewer" }
mcp__hyrex__agent_spawn { type: "coder", name: "Version Manager" }
mcp__hyrex__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__hyrex__task_orchestrate {
task: "Prepare release v1.0.72 with comprehensive testing and validation",
strategy: "sequential",
priority: "critical"
}
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.
- 14d ago First seen · 372 lines · 16 tokens per session scan A 1f0b25f99bb0
agent-release-manager is a skill published in the GitHub repository akhilyad/deployy (0 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 3,133 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to agent-release-manager, differing in 46 lines, and is treated as a copy.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.