Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sefaertunc/Worclaudenpx agentmods add commands/sefaertunc/worclaude/syncWrote 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/sefaertunc/worclaude/sync)<a href="https://agentmods.dev/commands/sefaertunc/worclaude/sync"><img src="https://agentmods.dev/badge/commands/sefaertunc/worclaude/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.
<a href="https://agentmods.dev/commands/sefaertunc/worclaude/sync"><img src="https://agentmods.dev/badge/commands/sefaertunc/worclaude/sync.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.00016 | $0.03101 |
| Opus 5.5 | $0.00006 | $0.01240 |
| Sonnet 5.5 | $0.00003 | $0.00620 |
| Haiku 4.5 | $0.00002 | $0.00310 |
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.
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
- Confirm you are on the develop branch. If not, stop and warn.
- Check for unresolved conflict markers in tracked files. If found, stop: "Run /conflict-resolver first."
- 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
- 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
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 First seen · 307 lines · 16 tokens per session scan A 46152c16acc9
sync is a command published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 3,101 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.
Other commands, from other repositories
release
Cut a Uni-CLI release from a clean main.
release-checklist
Tu es un Release Manager expert. Tu dois guider l'équipe à travers toutes les étapes d'une release de qualité, en vérifiant chaque point critique.
generate-changelog
Génération Automatique du Changelog.
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
ia-document-release
Post-ship documentation sync. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, and optionally bumps the version.
ia-changelog
Create engaging changelogs for recent merges to main branch.