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.
git clone --depth 1 https://github.com/ruvnet/ruv-FANNWrote 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/ruv-fann/release)<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/release"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/release/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/ruv-fann/release"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/release.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.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/github release
Releases a claimed GitHub issue back to the available pool, allowing other swarms to claim it.
Usage
/github release <issue_number> [reason]
Arguments
<issue_number>- Issue to release (required)[reason]- Why you're releasing it (optional but recommended)
Examples
/github release 45
/github release 45 "Blocked by dependency"
/github release 45 "Need expertise in WASM optimization"
/github release 45 "Higher priority task came up"
When to Release
- Blocked by dependencies
- Realized you lack required expertise
- Higher priority work emerged
- Can't complete within reasonable time
- Found it's duplicate of another issue
Implementation
Uses GitHub MCP to:
- Verify you currently own the task
- Remove
swarm-claimedlabel - Post release comment with reason
- Make task available again
Example Interactions
Basic Release
> /github release 45
🔓 Released issue #45
Task now available for other swarms
With Reason
> /github release 45 "Need WASM expertise - better suited for specialized swarm"
🔓 Released issue #45
Posted: "Released - Need WASM expertise"
Suggested area: wasm specialists
With Handoff
> /github release 45 "Partially complete - see PR #120 for progress so far"
🔓 Released issue #45
Posted handoff notes for next swarm
Progress preserved in PR #120
Release Message Format
🔓 Task Released by swarm `<your-id>`
Reason: <your reason>
Progress made:
- Analyzed the issue
- Started implementation
- See branch: feature/issue-45
Available for other swarms to continue.
---
Released at: <timestamp>
Best Practices
- Always provide a reason
- Document any progress made
- Link to branches/PRs with partial work
- Suggest what expertise is needed
- Release promptly when blocked
Partial Work
If you made progress:
- Push your branch
- Create draft PR
- Reference in release message
- Help next swarm continue
Related Commands
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.
- 12d ago First seen · 108 lines · 0 tokens per session scan A 0106bfb07fb5
release is a command published in the GitHub repository ruvnet/ruv-FANN (380 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 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.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
ship
Deploy feature through automated staging validation to production with rollback testing.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.