sync

A command that updates shared project progress, specification, and version files after pull requests are merged into the develop branch.

In plain words
What is it for?
Use it on develop after merges to review the changes, run the project's drift check, and update only PROGRESS.md, SPEC.md, and the version.
Why use it?
It keeps project status synchronized after merges and stops early when the branch or repository has unresolved conflicts.

Command for Claude Code

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/sefaertunc/worclaude/sync
Clone the repo
git clone --depth 1 https://github.com/sefaertunc/Worclaude

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,101 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.00016 $0.03101
Opus 5 $0.00008 $0.01550
Sonnet 5 $0.00003 $0.00620
Haiku 4.5 $0.00002 $0.00310

Measured 2d ago against content hash 46152c16acc9, 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 2d 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.

.claude/commands/sync.md · 307 lines

How it starts

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

Update shared-state files after merging feature PRs into develop. Run this on the develop branch AFTER all PRs are merged and any conflicts are resolved.

ONLY update shared-state files — do not resolve conflicts. That is /conflict-resolver's job. If you detect unresolved conflicts, stop and tell the user to run /conflict-resolver first.

Invocation Contract

Run this command only when the human explicitly invokes it (typed /sync or one of the Trigger Phrases at the bottom of this file). Do not auto-launch after detecting that PRs were merged. The "ship/wait" prompt at step 9 is non-skippable. See CLAUDE.md Critical Rule 13.

Pre-check

  1. Confirm you are on the develop branch. If not, stop and warn.
  2. Check for unresolved conflict markers in tracked files. If found, stop: "Run /conflict-resolver first."
  3. Read git log to understand what was merged since the last sync or version tag. If nothing was merged, report "Nothing to sync" and stop.

Drift preflight

3a. Run worclaude doctor to surface CLAUDE.md ↔ package.json drift before any shared-state file writes:

```bash
worclaude doctor
```

The `## Documentation` section reports any tech-stack claims in
CLAUDE.md (e.g., `857 tests, 62 files`) that no longer match the
current test count. If a `CLAUDE.md test-file count drift` warning
appears, step 10c will fix the line when it refreshes tech-stack
metrics — note the actual count from the warning and proceed.

If the warning is surprising (claim doesn't exist, or the delta is
large enough to suggest a deleted/renamed suite), pause and inspect
before continuing. Other doctor warnings are advisory; only the
drift warning is load-bearing for this sync.

Update PROGRESS.md

  1. Update docs/spec/PROGRESS.md:
    • Mark completed items based on merged work
    • Update "Last Updated" date to today
    • Update Stats section by checking actual project values (run the test suite, count source files, etc.)
    • Move "In Progress" items to "Completed" if their PRs merged
    • Update "Next Steps" if needed

Read the full file on GitHub · 307 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. 2d ago First seen · 307 lines · 16 tokens per session scan A 46152c16acc9

Subscribe to this mod's changes

sync is a command published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 23d ago), licensed MIT. It adds 16 tokens to every session and 3,101 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.