A workspace-sync command that fetches updates and rebases the current workspace onto the project’s trunk branch. A rebase reapplies your local work on top of newer upstream changes.

Use it before continuing development or integrating changes, especially when working across multiple repositories or workspaces.

It brings a workspace up to date and reports conflicts when your changes overlap with incoming work.

sync — Command by mdsakalu

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/mdsakalu/agent-plugins/sync

Clone the repo

git clone --depth 1 https://github.com/mdsakalu/agent-plugins

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 453 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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00453
Opus 5	$0.00006	$0.00227
Sonnet 5	$0.00003	$0.00091
Haiku 4.5	$0.00001	$0.00045

Measured yesterday against content hash face48470315, 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.

workspace/commands/sync.md · 47 lines

What it actually says

Sync a workspace with upstream (fetch and rebase onto trunk).

Resolve the metarepo path by reading ~/.claude/workspace-config.json and expanding ~ to $HOME.

The user's request: $ARGUMENTS

Steps

Read ~/.claude/workspace-config.json to get the metarepo path. Expand ~ to $HOME.
Determine which workspace to sync:
- If <repo>/<workspace> specified, use <metarepo>/repos/<repo>/<workspace>/
- If just <workspace>, search across repos
- If no argument, infer from cwd (match */repos/<repo>/<workspace>*)
- If unable to determine, list workspaces and ask
Verify the workspace directory exists and has JJ initialized.
Run from the workspace directory:
```
jj git fetch
```
Rebase onto trunk using the repo's trunk alias:
```
jj rebase -d trunk()
```
If trunk() fails, fall back to reading default_branch from <metarepo>/repos/<repo>/.repo.json and use <default_branch>@origin.
Check for conflicts in the rebase output. If conflicts:
- Report them clearly
- Suggest jj status and jj diff to inspect
- Suggest manual conflict resolution
Show the result:
```
jj log --limit 5
```
Report success or issues.

Important

Always resolve metarepo from ~/.claude/workspace-config.json, never hardcode paths.
Workspaces live at <metarepo>/repos/<repo>/<workspace>/.
Use trunk() revset alias (set during add-repo) for the rebase destination.
JJ handles uncommitted changes transparently during rebase.
Conflicts are reported but don't stop the operation.

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.

yesterday First seen · 47 lines · 13 tokens per session scan A face48470315

Subscribe to this mod's changes

sync is a command published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 453 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-08-31.

Git and workflow

sync

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Steps

Important

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement