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/setup)<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/setup"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/setup/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/setup"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/setup.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.00987 |
| Opus 5 | $0.00000 | $0.00494 |
| Sonnet 5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade B, and why
setup scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install gh How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Swarm Coordination Setup
Quick setup guide for GitHub-based swarm coordination in Claude Code.
Prerequisites
-
GitHub MCP server installed:
claude mcp add github "npx @modelcontextprotocol/server-github" -
GitHub CLI installed (optional but recommended):
# macOS brew install gh # Linux sudo apt install gh # Then authenticate gh auth login
Configuration
1. Set Your Swarm ID
# In your shell or .env
export CLAUDE_SWARM_ID="my-unique-swarm-id"
# Or let it auto-generate
export CLAUDE_SWARM_ID="swarm-$(date +%s)"
2. Configure Repository
# Set default repo for commands
export GITHUB_OWNER="ruvnet"
export GITHUB_REPO="ruv-FANN"
3. Add Command Aliases (Optional)
Add to your shell profile:
# Quick GitHub swarm commands
alias swarm-status="/github status"
alias swarm-tasks="/github tasks"
alias swarm-claim="/github claim"
alias swarm-update="/github update"
First Time Usage
-
Check system status:
/github status -
Find available work:
/github tasks --priority high -
Claim your first task:
/github claim <issue_number> -
Update progress:
/github update <issue_number> "Started implementation"
Label Setup (For Maintainers)
Create these labels in your GitHub repo:
# Priority labels
gh label create "priority: critical" --color FF0000
gh label create "priority: high" --color FFA500
gh label create "priority: medium" --color FFFF00
gh label create "priority: low" --color 808080
# Area labels
gh label create "area: core" --color 0052CC
gh label create "area: mcp" --color 5319E7
gh label create "area: neural" --color 206B38
gh label create "area: wasm" --color B60205
gh label create "area: docs" --color 1D76DB
# Coordination labels
gh label create "available" --color 0E8A16
gh label create "swarm-claimed" --color F9D0C4
gh label create "help-wanted" --color 008672
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 · 175 lines · 0 tokens per session scan B 5f357bb7449f
setup 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 987 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.