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/monoes/monomindWrote 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/monoes/monomind/sync-coordinator)<a href="https://agentmods.dev/commands/monoes/monomind/sync-coordinator"><img src="https://agentmods.dev/badge/commands/monoes/monomind/sync-coordinator/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/monoes/monomind/sync-coordinator"><img src="https://agentmods.dev/badge/commands/monoes/monomind/sync-coordinator.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.00024 | $0.02413 |
| Opus 5.5 | $0.00010 | $0.00965 |
| Sonnet 5.5 | $0.00005 | $0.00483 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
github: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.
This is a copy
83% identical to sync-coordinator — 125 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 296 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 monomind swarm coordination for seamless integration across 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__monomind__*(all swarm coordination tools)TodoWrite,TodoRead,Task,Bash,Read,Write,Edit,MultiEdit
Usage Patterns
1. Synchronize Package Dependencies
// Spawn sync coordination agents
mcp__monomind__agent_spawn { type: "coordinator", name: "Sync Coordinator" }
mcp__monomind__agent_spawn { type: "analyst", name: "Dependency Analyzer" }
mcp__monomind__agent_spawn { type: "coder", name: "Integration Developer" }
mcp__monomind__agent_spawn { type: "tester", name: "Validation Engineer" }
// Analyze current package states
Read("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/packages/@monomind/cli/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/packages/@monomind/cli/package.json?ref=sync/package-alignment --jq '.sha')")`)
// Orchestrate validation
mcp__monomind__task_create {
description: "Validate package synchronization and run integration tests",
agents: ["coordinator", "analyst", "tester"],
strategy: "parallel"
}
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 · 296 lines · 24 tokens per session scan A e5270985060d
github:sync-coordinator is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 2,413 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to sync-coordinator, differing in 125 lines, and is treated as a copy.
Other commands, from other repositories
swarm-init
Initialize a Claude Flow swarm with specified topology and configuration.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.