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 commands/ruvnet/ruview/sync-coordinatorgit clone --depth 1 https://github.com/ruvnet/RuViewWhat 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.00000 | $0.02707 |
| Opus 5 | $0.00000 | $0.01354 |
| Sonnet 5 | $0.00000 | $0.00541 |
| Haiku 4.5 | $0.00000 | $0.00271 |
Grade A, and why
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
8 near-identical copies found in the catalogue:
- sync-coordinator — 100% identical, 0 lines differ
- sync-coordinator — 100% identical, 0 lines differ
- sync-coordinator — 100% identical, 0 lines differ
- sync-coordinator — 100% identical, 0 lines differ
- sync-coordinator — 100% identical, 0 lines differ
- sync-coordinator — 100% identical, 0 lines differ
- sync-coordinator — 100% identical, 0 lines differ
- sync-coordinator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
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
Usage Patterns
1. Synchronize Package Dependencies
// Initialize sync coordination swarm
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 5 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Sync Coordinator" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Dependency Analyzer" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Integration Developer" }
mcp__claude-flow__agent_spawn { type: "tester", name: "Validation Engineer" }
// Analyze current package states
Read("/workspaces/ruv-FANN/claude-code-flow/claude-code-flow/package.json")
Read("/workspaces/ruv-FANN/ruv-swarm/npm/package.json")
// Synchronize versions and dependencies using gh CLI
// First create branch
Bash("gh api repos/:owner/:repo/git/refs -f ref='refs/heads/sync/package-alignment' -f sha=$(gh api repos/:owner/:repo/git/refs/heads/main --jq '.object.sha')")
// Update file using gh CLI
Bash(`gh api repos/:owner/:repo/contents/claude-code-flow/claude-code-flow/package.json \
--method PUT \
-f message="feat: Align Node.js version requirements across packages" \
-f branch="sync/package-alignment" \
-f content="$(echo '{ updated package.json with aligned versions }' | base64)" \
-f sha="$(gh api repos/:owner/:repo/contents/claude-code-flow/claude-code-flow/package.json?ref=sync/package-alignment --jq '.sha')")`)
// Orchestrate validation
mcp__claude-flow__task_orchestrate {
task: "Validate package synchronization and run integration tests",
strategy: "parallel",
priority: "high"
}
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 · 301 lines · 0 tokens per session scan A 197e5b633bd2
sync-coordinator is a command published in the GitHub repository ruvnet/RuView (92,079 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,707 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
fix_board
Automatically diagnose and fix PlatformIO board upload/monitor issues.
test
Run tests using uv run test.py with optional arguments.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
gh-pr
Create (or update) a Pull Request.
gh-review
Address feedback and checks in a Pull Request.
checkpoint
Create a checkpoint by staging the changes you have made using git. usage: git [-v | --version] [-h | --help] [-C ] [-c = ] [--exec-path[= ]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir= ] [--work-tree= ] [--namespace= ] [--super-prefix= ]…