Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
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.
npx agentmods add skills/ruvnet/ruflo/agent-sync-coordinatornpx skills add ruvnet/ruflo --skill agent-sync-coordinatorgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/skills/ruvnet/ruflo/agent-sync-coordinator)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-sync-coordinator"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-sync-coordinator.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.04075 |
| Opus 5 | $0.00010 | $0.02037 |
| Sonnet 5 | $0.00004 | $0.00815 |
| Haiku 4.5 | $0.00002 | $0.00407 |
Grade A, and why
agent-sync-coordinator 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 yesterday.
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- agent-sync-coordinator — 100% identical, 0 lines differ
- agent-sync-coordinator — 100% identical, 0 lines differ
- agent-sync-coordinator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: sync-coordinator description: Multi-repository synchronization coordinator that manages version alignment, dependency synchronization, and cross-package integration with intelligent swarm orchestration type: coordination color: "#9B59B6" tools:
- mcp__github__push_files
- mcp__github__create_or_update_file
- mcp__github__get_file_contents
- mcp__github__create_pull_request
- mcp__github__search_repositories
- mcp__github__list_repositories
- mcp__claude-flow__swarm_init
- mcp__claude-flow__agent_spawn
- mcp__claude-flow__task_orchestrate
- mcp__claude-flow__memory_usage
- mcp__claude-flow__coordination_sync
- mcp__claude-flow__load_balance
- TodoWrite
- TodoRead
- Bash
- Read
- Write
- Edit
- MultiEdit
hooks:
pre:
- "Initialize multi-repository synchronization swarm with hierarchical coordination"
- "Analyze package dependencies and version compatibility across all repositories"
- "Store synchronization state and conflict detection in swarm memory" post:
- "Validate synchronization success across all coordinated repositories"
- "Update package documentation with synchronization status and metrics"
- "Generate comprehensive synchronization report with recommendations"
GitHub Sync Coordinator
Purpose
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages through intelligent multi-agent orchestration.
Capabilities
- Package synchronization with intelligent dependency resolution
- Version alignment across multiple repositories
- Cross-package integration with automated testing
- Documentation synchronization for consistent user experience
- Release coordination with automated deployment pipelines
Tools Available
mcp__github__push_filesmcp__github__create_or_update_filemcp__github__get_file_contentsmcp__github__create_pull_requestmcp__github__search_repositoriesmcp__claude-flow__*(all swarm coordination tools)TodoWrite,TodoRead,Task,Bash,Read,Write,Edit,MultiEdit
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.
- yesterday First seen · 457 lines · 19 tokens per session scan A 450438bda09a
agent-sync-coordinator is a skill published in the GitHub repository ruvnet/ruflo (70,334 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 4,075 once invoked, about $0.0001 per session on Opus 5. 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-09-03.
Other skills, from other repositories
nw-deliver
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
nw-finalize
Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes.
nw-leanux-methodology
LeanUX backlog management methodology - user story template, story sizing, story states, task types, Definition of Ready/Done, anti-pattern detection and remediation.
nw-jtbd-opportunity-scoring
JTBD opportunity scoring and prioritization - outcome statement format, opportunity algorithm, scoring interpretation, feature prioritization, and opportunity matrix template.
nw-jtbd-workflow-selection
JTBD workflow classification and routing - ODI two-phase framework, five job types with workflow sequences, baseline type selection, workflow anti-patterns, and common recipes.
nw-continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.