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/claim)<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/claim"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/claim/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/claim"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/claim.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.00445 |
| Opus 5.5 | $0.00000 | $0.00178 |
| Sonnet 5.5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
claim 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.
What it actually says
/github claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
Usage
/github claim <issue_number> [message]
Arguments
<issue_number>- The GitHub issue number to claim (required)[message]- Optional message about your plan (default: auto-generated)
Examples
/github claim 45
/github claim 45 "Will focus on memory optimization using new WASM features"
What it does
- Checks if the issue is available (not already claimed)
- Adds
swarm-claimedlabel to the issue - Posts a comment with:
- Your swarm ID
- Work plan (if provided)
- Estimated completion time
- Updates local tracking
Implementation
Uses GitHub MCP to:
- Get current issue state
- Verify no existing
swarm-claimedlabel - Update labels to include
swarm-claimed - Add comment with claim details
Example Interaction
> /github claim 45
🎯 Claiming issue #45...
✅ Successfully claimed issue #45: "Implement memory optimization"
Posted comment:
🐝 Swarm ID: `claude-abc-123` claiming this task.
Plan:
1. Analyze current memory usage patterns
2. Implement optimization strategies
3. Add memory benchmarks
4. Update documentation
ETA: 2-3 hours
The issue is now locked to your swarm. Remember to post updates!
Error Cases
- Issue already claimed: Shows current owner and suggests coordination
- Issue closed: Suggests finding another task
- Issue not found: Verifies issue number
Best Practices
- Only claim tasks you can complete
- Release tasks if blocked
- Post updates regularly
- Complete or release within 24 hours
Related Commands
/github tasks- Find available tasks/github update <number>- Post progress/github release <number>- Release if needed/github complete <number>- Mark as done
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 · 82 lines · 0 tokens per session scan A a7a8239ce4b7
claim is a command published in the GitHub repository ruvnet/ruv-FANN (387 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 445 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
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.