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/swarms)<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/swarms"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/swarms/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/swarms"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/swarms.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.00797 |
| Opus 5 | $0.00000 | $0.00398 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
swarms 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 9d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/github swarms
Lists all active swarms working on the project, showing what each is working on and coordination opportunities.
Usage
/github swarms [options]
Options
--active- Only show recently active swarms (default)--all- Include inactive swarms--conflicts- Highlight potential conflicts
Examples
/github swarms
/github swarms --all
/github swarms --conflicts
What it shows
- Active swarm IDs
- Current tasks per swarm
- Last activity time
- Work areas/expertise
- Potential collaboration opportunities
Implementation
Uses GitHub MCP to:
- Find all issues with swarm claims
- Group by swarm ID
- Analyze activity patterns
- Identify collaboration opportunities
Example Output
Basic View
🐝 Active Swarms (5)
swarm-alpha-123 (Active now)
├─ Working on: #45 Memory optimization
├─ Last seen: 5 min ago
└─ Focus: Performance, WASM
swarm-beta-456 (Active)
├─ Working on: #52 Neural agent fixes
├─ Last seen: 1 hour ago
└─ Focus: Neural networks, AI
swarm-gamma-789 (Active)
├─ Working on: #48 Documentation
├─ Working on: #49 Examples
├─ Last seen: 30 min ago
└─ Focus: Documentation, Testing
swarm-delta-012 (Idle)
├─ No current tasks
├─ Last seen: 3 hours ago
└─ Focus: Unknown
swarm-epsilon-345 (Inactive)
├─ Stale claim: #38 (2 days old)
├─ Last seen: 2 days ago
└─ Status: Consider releasing task
With Conflicts View
🐝 Active Swarms - Conflict Analysis
⚠️ Potential Conflicts Detected:
1. File Overlap:
swarm-alpha-123 and swarm-beta-456
Both modifying: src/neural-agent.js
Suggestion: Coordinate via issue comments
2. Related Tasks:
swarm-gamma-789 working on #48 (docs)
swarm-zeta-678 working on #50 (examples)
Suggestion: Align documentation approach
🤝 Collaboration Opportunities:
- swarm-alpha-123 + swarm-beta-456:
Both working on performance issues
Could share benchmarking approach
- swarm-gamma-789 + swarm-delta-012:
Delta is idle, Gamma has 2 doc tasks
Could help with documentation
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.
- 9d ago First seen · 139 lines · 0 tokens per session scan A 7f92c261979e
swarms 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 797 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.