sync

A command for sharing code changes and selected configuration files between Git worktrees, which are separate working folders connected to the same repository.

In plain words
What is it for?
Use it to distribute branch changes, synchronize environment variables and configuration files, apply file-sync presets, or update all selected worktrees.
Why use it?
It avoids manually copying changes or environment files between parallel working folders. You can choose specific worktrees, filter them, and merge or rebase the changes.

Command

Install

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.

agentmods
npx agentmods add commands/mirinodev/maestro/sync
Clone the repo
git clone --depth 1 https://github.com/mirinodev/maestro
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02304
Opus 5 $0.00000 $0.01152
Sonnet 5 $0.00000 $0.00461
Haiku 4.5 $0.00000 $0.00230

Measured yesterday against content hash bb95d51ee865, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sync 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.

docs/commands/sync.md · 411 lines

How it starts

The opening of the file, as written. The whole thing — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🔸 sync

Command to synchronize code and configuration files between orchestra members (Git worktrees). You can reflect changes from the main branch to other orchestra members or share environment configuration files.

Overview

mst sync [branch-name] [options]
mst s [branch-name] [options]  # alias

Usage Examples

Basic Usage

# Sync changes from main branch to specific orchestra member
mst sync feature-branch

# Sync to all orchestra members
mst sync --all

# Interactive selection (path display follows ui.pathDisplay configuration)
mst sync

# Sync with rebase (default is merge)
mst sync --rebase

Filtering Orchestra Members

# Filter by keyword (branch name or path)
mst sync --filter feature --all

# Filter by wildcard pattern
mst sync --pattern "feature/*" --all
mst sync --pattern "bugfix-*" --all

# Combine filters (AND condition)
mst sync --filter api --pattern "feature/*" --all

# Use with fzf for interactive selection from filtered results
mst sync --filter feature --fzf

File Synchronization

# Sync environment variables and configuration files
mst sync --files

# Use presets for file sync
mst sync --preset env     # .env files only
mst sync --preset config  # configuration files only
mst sync --preset all     # all configuration files

# Interactive file selection
mst sync --interactive

Options

Option Short Description Default
--all -a Sync to all orchestra members false
--main <branch> -m Specify main branch auto-detect
--fzf Select orchestra members with fzf false
--rebase Sync with rebase (default is merge) false
--dry-run Show changes without actually syncing false
--push Push after merge/rebase false
--filter <keyword> Filter worktrees by branch/path none
--pattern <pattern> Filter by wildcard pattern none
--files -f File sync mode false
--preset <name> -p Use preset for file sync none
--interactive -i Interactive file selection false
--concurrency <n> -c Parallel execution count 5

Read the full file on GitHub · 411 lines

Changes

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.

  1. yesterday First seen · 411 lines · 0 tokens per session scan A bb95d51ee865

Subscribe to this mod's changes

sync is a command published in the GitHub repository mirinodev/maestro (9 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,304 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-31.