coordinate

coordinate is a command for Claude Code from ruvnet/ruv-FANN. It costs 0 tokens per session (756 once invoked), scanned A, original, MIT.

A command for planning how several groups of agents should work together on GitHub issues. It can suggest splitting, combining, ordering, or pairing issues.

In plain words
What is it for?
Splitting large issues, merging related issues, ordering dependent work, and requesting collaboration between swarms.
Why use it?
It helps turn a large issue into smaller tasks and makes dependencies or collaboration needs explicit. It can also post coordination proposals as GitHub comments.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Splitting large issues, merging related issues, ordering dependent work, and requesting collaboration between swarms.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ruvnet/ruv-fann/coordinate
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ruvnet/ruv-FANN

Made for: Claude Code.

Wrote 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.

agentmods badge for coordinate

README.md
[![agentmods](https://agentmods.dev/badge/commands/ruvnet/ruv-fann/coordinate/github.svg)](https://agentmods.dev/commands/ruvnet/ruv-fann/coordinate)
Your own site
<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/coordinate"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/coordinate/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.

agentmods 80×15 button for coordinate

Your own site · 80×15
<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/coordinate"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/coordinate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 756 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00756
Opus 5.5 $0.00000 $0.00302
Sonnet 5.5 $0.00000 $0.00151
Haiku 4.5 $0.00000 $0.00076

Measured 2mo ago against content hash 6e06e14e46b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coordinate 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 2mo 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.

.claude/commands/github/coordinate.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/github coordinate

Helps coordinate work between multiple swarms by proposing task splits, dependencies, or collaborative approaches.

Usage

/github coordinate <action> [options]

Actions

  • split <issue> - Propose splitting a large issue
  • merge <issue1> <issue2> - Suggest combining related issues
  • sequence <issues...> - Propose order for dependent tasks
  • pair <issue> - Request collaboration on complex task

Examples

/github coordinate split 45
/github coordinate merge 45 46
/github coordinate sequence 51 52 53
/github coordinate pair 60 --with swarm-beta-456

Implementation

Uses GitHub MCP to:

  1. Analyze issue complexity
  2. Identify relationships
  3. Create coordination proposals
  4. Post collaboration comments

Example Interactions

Task Splitting

> /github coordinate split 45

📊 Analyzing issue #45: "Implement complete authentication system"

Suggested split into 3 tasks:

1. **Backend Authentication API**
   - JWT token generation
   - User validation
   - Session management
   
2. **Frontend Auth Components**  
   - Login/signup forms
   - Auth state management
   - Route protection
   
3. **Testing & Documentation**
   - Integration tests
   - API documentation
   - Usage examples

Posted coordination proposal to issue #45
Other swarms can claim subtasks

Task Sequencing

> /github coordinate sequence 51 52 53

📋 Dependency Analysis:

Suggested sequence:
1. #51: Database schema (Required first)
2. #52: API endpoints (Needs schema)  
3. #53: UI components (Needs API)

Dependencies posted to all three issues
Swarms should complete in order

Pairing Request

> /github coordinate pair 60 --with swarm-beta-456

🤝 Collaboration Proposal for #60:

Requesting pair work with swarm-beta-456
Task: Complex WASM optimization

Proposed split:
- Your swarm: Performance profiling
- Beta swarm: Implementation
- Both: Testing & validation

Posted collaboration request
Waiting for response from swarm-beta-456

Read the full file on GitHub · 163 lines

Changes

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.

  1. 2mo ago First seen · 163 lines · 0 tokens per session scan A 6e06e14e46b1

Subscribe to this mod's changes

coordinate is a command published in the GitHub repository ruvnet/ruv-FANN (387 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 756 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.

Related

coordinate compared with commands from other repositories

coordinate next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
coordinateruvnet/ruv-FANNCommand3873mo agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code