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/update)<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/update"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/update/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/update"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/update.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.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
update 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.
What it actually says
/github update
Posts a progress update to a claimed GitHub issue, keeping other swarms informed of your progress.
Usage
/github update <issue_number> <message>
Arguments
<issue_number>- The issue you're updating (required)<message>- Progress update message (required)
Examples
/github update 45 "Completed memory analysis, found 3 leak sources"
/github update 45 "50% done - implemented fixes, testing now"
/github update 45 "Blocked by #52, waiting for neural agent fixes"
Progress Indicators
Use these prefixes for clarity:
✅- Completed items🔄- In progress⏳- Pending❌- Blocked⚠️- Issues found
Implementation
Uses GitHub MCP to:
- Verify you own the claimed task
- Post formatted comment with progress
- Update last activity timestamp
- Check for staleness warnings
Example Interactions
Simple Update
> /github update 45 "Implemented first optimization pass"
📝 Posted update to issue #45
Detailed Update
> /github update 45 "Major progress on memory optimization:
✅ Analyzed memory patterns
✅ Identified 3 leak sources
🔄 Implementing fixes (70% done)
⏳ Tests pending
⏳ Documentation update"
📝 Posted detailed update to issue #45
Blocked Update
> /github update 45 "Blocked: Need PR #52 merged first"
⚠️ Posted blocked status to issue #45
Consider releasing if blocked for long?
Auto-Generated Format
Updates are posted as:
🔄 Progress Update from swarm `<your-id>`:
<your message>
---
Updated at: <timestamp>
Best Practices
- Update at least every hour when working
- Be specific about what you've done
- Mention blockers immediately
- Reference related issues/PRs
- Give completion estimates
Related Commands
/github claim <number>- Claim a task first/github complete <number>- Mark as done/github release <number>- Release if blocked/github my-tasks- See your tasks
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 · 95 lines · 0 tokens per session scan A 3fe222c8195a
update 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 497 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
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.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
afo
Open feature worktree in terminal and start agent (shortcut for feature-open).