agentmods.dev

sync

sync is a command for Claude Code from mdsakalu/agent-plugins. It costs 13 tokens per session (453 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
Use it before continuing development or integrating changes, especially when working across multiple repositories or workspaces.
Why use it?
It brings a workspace up to date and reports conflicts when your changes overlap with incoming work.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Part of the workspace plugin — 13 commands, 3 hooks shipped together

not rated 4repo 4mo ago A scan 13 tokens original MIT

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

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/mdsakalu/agent-plugins/sync
View source ↗ mdsakalu/agent-plugins
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.

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

Made for: Claude Code.

Or install workspace, the plugin that ships this one along with the rest of its 13 commands, 3 hooks.

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

agentmods badge for sync

README.md
[![agentmods](https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/sync/github.svg)](https://agentmods.dev/commands/mdsakalu/agent-plugins/sync)
Your own site
<a href="https://agentmods.dev/commands/mdsakalu/agent-plugins/sync"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/sync/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.

agentmods 80×15 button for sync

Your own site · 80×15
<a href="https://agentmods.dev/commands/mdsakalu/agent-plugins/sync"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00013 $0.00453
Opus 5.5 $0.00005 $0.00181
Sonnet 5.5 $0.00003 $0.00091
Haiku 4.5 $0.00001 $0.00045

Measured 1mo ago against content hash face48470315, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

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

  1. Read ~/.claude/workspace-config.json to get the metarepo path. Expand ~ to $HOME.
  2. 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
  3. Verify the workspace directory exists and has JJ initialized.
  4. Run from the workspace directory: 
    jj git fetch
  5. 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.
  6. Check for conflicts in the rebase output. If conflicts:
    • Report them clearly
    • Suggest jj status and jj diff to inspect
    • Suggest manual conflict resolution
  7. Show the result: 
    jj log --limit 5
  8. 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.

  1. 1mo ago 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 4mo ago), licensed MIT. It adds 13 tokens to every session and 453 once invoked, about $0.0001 per session on Opus 5.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
Related

Other commands, from other repositories

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

pr

Handle the full workflow from current branch state to an open, CI-monitored pull request.

opsmill/infrahub-mcp · 18 tokens

codex-review

Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.

oalders/kitchen-sink · 41 tokens