Borrowing it
Nothing to install: this file belongs to design-and-deliver/claude-code-autoconfig. 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/design-and-deliver/claude-code-autoconfig/main/.claude/commands/sync-worktrees.mdgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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/design-and-deliver/claude-code-autoconfig/sync-worktrees)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/sync-worktrees"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/sync-worktrees/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/design-and-deliver/claude-code-autoconfig/sync-worktrees"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/sync-worktrees.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.01534 |
| Opus 5.5 | $0.00000 | $0.00614 |
| Sonnet 5.5 | $0.00000 | $0.00307 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
sync-worktrees 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-worktrees
/fleet tells you who is working where. This is its write counterpart: the thing that cleans up
after the worktree loop is done.
The specific mess it exists for: ExitWorktree remove de-registers a worktree and then deletes its
tree. On Windows the second half loses — something holds a handle inside node_modules (esbuild,
vite, a watcher), the recursive delete aborts, and git has already forgotten the entry. So the
directory becomes invisible to git forever:
git worktree list → only the base checkout
git worktree prune → nothing to do
.claude/worktrees/ → five full working trees, node_modules and all
prune is not the fix. Orphans are found by walking .claude/worktrees/ and subtracting what
git still knows about.
Step 1 — run it
node "${CLAUDE_PROJECT_DIR:-.}/.claude/scripts/sync-worktrees.js"
Default is a dry run. Always run the bare form first, even when $ARGUMENTS contains write.
⛔ Before any --write, in this order:
- Snapshot every worktree:
node scripts/snapshot-worktrees.js C:\CODE\claude-code-autoconfig C:\CODE\job-agent-extension(from the CCA checkout). Note the backup folder it prints. - Run the dry run and show the user its output, the REGISTERED WORKTREES list above all:
each
RECLAIMrow there is a registered worktree--writewill remove. - Run
--writeonly after the user says yes to that list. An approval from an earlier run doesn't count, because other sessions keep working in between.
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 Changed · +14 lines 73f8336aa1a9
- 2mo ago First seen · 87 lines · 0 tokens per session scan A 72540c79b029
sync-worktrees is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,534 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.
Other commands, from other repositories
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
git-ops
Git + worktree orchestrator entry point. /git-ops --landall surveys every branch/worktree and batch-lands the ones that are done; bare /git-ops runs a status survey. Thin router over the git-ops skill.
branch
Show Claude Code costs per git branch / PR.