Borrowing it
Nothing to install: this file belongs to ArieGoldkin/ai-agent-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ArieGoldkin/ai-agent-hub/main/.squad/commands/sync-parallel.mdgit clone --depth 1 https://github.com/ArieGoldkin/ai-agent-hubWrote 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/ariegoldkin/ai-agent-hub/sync-parallel)<a href="https://agentmods.dev/commands/ariegoldkin/ai-agent-hub/sync-parallel"><img src="https://agentmods.dev/badge/commands/ariegoldkin/ai-agent-hub/sync-parallel/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/ariegoldkin/ai-agent-hub/sync-parallel"><img src="https://agentmods.dev/badge/commands/ariegoldkin/ai-agent-hub/sync-parallel.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.02181 |
| Opus 5.5 | $0.00000 | $0.00872 |
| Sonnet 5.5 | $0.00000 | $0.00436 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
sync-parallel 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Parallel Agent Execution
Coordinate and synchronize multiple agents working in parallel, detect conflicts, and reassign work as needed.
Primary Responsibilities
- Read all active communication files
- Identify completed tasks and blockers
- Detect and resolve conflicts
- Reassign work if needed
- Generate comprehensive status reports
Synchronization Protocol
Step 1: Gather Agent Status
# Read all communication files
for comm_file in .squad/comms/agent-*-comm.md; do
agent_id=$(basename "$comm_file" -comm.md)
status=$(grep "^Status:" "$comm_file" | tail -1 | cut -d: -f2)
echo "$agent_id: $status"
done
Step 2: Analyze Current State
## Parallel Execution State Analysis
### Active Agents
| Agent ID | Status | Current Task | Progress | Blockers |
|----------|--------|--------------|----------|----------|
| agent-1 | ACTIVE | Dashboard UI | 3/5 tasks | None |
| agent-2 | BLOCKED | API endpoints | 2/4 tasks | Waiting for types |
| agent-3 | ACTIVE | ML pipeline | 1/3 tasks | None |
### File Lock Status
| File | Locked By | Duration | Status |
|------|-----------|----------|--------|
| /frontend/Dashboard.tsx | agent-1 | 2 min | Active |
| /shared/types/metrics.ts | agent-1 | 8 min | ⚠️ Long |
### Completed Tasks
- ✅ Frontend layout structure (agent-1)
- ✅ Database schema (agent-2)
- ✅ Base ML model selection (agent-3)
Step 3: Detect Conflicts
# Conflict detection algorithm
def detect_conflicts():
conflicts = []
# Check for lock conflicts
for lock_file in locks:
if lock_duration > 10_minutes:
conflicts.append({
'type': 'STALE_LOCK',
'file': lock_file,
'agent': lock_owner,
'duration': lock_duration
})
# Check for file conflicts
modified_files = get_git_modified()
for file in modified_files:
owners = get_file_owners(file)
if len(owners) > 1:
conflicts.append({
'type': 'MULTIPLE_MODIFICATIONS',
'file': file,
'agents': owners
})
# Check for dependency blocks
for agent in blocked_agents:
if agent.blocked_duration > 15_minutes:
conflicts.append({
'type': 'LONG_BLOCK',
'agent': agent.id,
'waiting_for': agent.blocker,
'duration': agent.blocked_duration
})
return conflicts
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.
- 1mo ago First seen · 335 lines · 0 tokens per session scan A 47a5676ce2c1
sync-parallel is a command published in the GitHub repository ArieGoldkin/ai-agent-hub (12 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,181 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.