status

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

A GitHub status command for shared swarm work. It shows available and claimed issues, active swarms, coordination conflicts, and recent activity.

In plain words
What is it for?
Use it to review task priorities, inspect swarm assignments, find conflicts, and spot claims that have not been updated recently.
Why use it?
It makes it easier to see which tasks are free, which are already being handled, and where two swarms might overlap.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to review task priorities, inspect swarm assignments, find conflicts, and spot claims that have not been updated recently.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ruvnet/ruv-fann/status
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 status

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/status"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/status.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 351 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.00351
Opus 5 $0.00000 $0.00176
Sonnet 5 $0.00000 $0.00070
Haiku 4.5 $0.00000 $0.00035

Measured 12d ago against content hash 76ab9db2c95d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

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

.claude/commands/github/status.md · 57 lines

What it actually says

/github status

Shows the current swarm coordination status including available tasks, active swarms, and potential conflicts.

Usage

/github status

What it shows

  • Total available tasks by priority
  • Currently claimed tasks and their swarms
  • Active swarms and what they're working on
  • Any coordination conflicts
  • Recent activity summary

Implementation

This command uses the GitHub MCP to:

  1. List all open issues with coordination labels
  2. Group by swarm assignment
  3. Identify potential conflicts
  4. Show summary statistics

Example Output

🐝 Swarm Coordination Status

📊 Overview:
- Available Tasks: 12 (3 critical, 5 high, 4 medium)
- Claimed Tasks: 8
- Active Swarms: 4
- Conflicts: 0

🚀 Active Swarms:
- swarm-alpha-123: Working on #45 (Memory optimization)
- swarm-beta-456: Working on #52 (Neural agent fixes)
- swarm-gamma-789: Working on #48 (Documentation update)
- swarm-delta-012: Working on #50 (WASM performance)

📋 Available High Priority:
- #53: [BUG] Memory leak in pattern matching
- #54: [FEATURE] Add real-time metrics
- #55: [TASK] Refactor coordination system

⚠️ Stale Claims (>24h):
- #38: Last updated 2 days ago by swarm-old-999
  • /github tasks - List only available tasks
  • /github my-tasks - Show your swarm's tasks
  • /github swarms - Detailed swarm information
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. 12d ago First seen · 57 lines · 0 tokens per session scan A 76ab9db2c95d

Subscribe to this mod's changes

status 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 351 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.