sync

A command linked to a sync workflow file. The available information does not explain what the workflow synchronises.

In plain words
What is it for?
Running the referenced sync workflow. Its exact tasks cannot be determined from the description.
Why use it?
It may provide a repeatable sync step, but the available description is too limited to identify the problem it removes.

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/myths-labs/muse/sync
Clone the repo
git clone --depth 1 https://github.com/myths-labs/muse

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6 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.00000 $0.00006
Opus 5 $0.00000 $0.00003
Sonnet 5 $0.00000 $0.00001
Haiku 4.5 $0.00000 $0.00001

Measured 2d ago against content hash 2269dff8123f, 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 · 1 lines

What it actually says

../../workflows/sync.md

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 · 1 lines · 0 tokens per session scan A 2269dff8123f

Subscribe to this mod's changes

sync is a command published in the GitHub repository myths-labs/muse (32 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6 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-30.

Related

Other commands, from other repositories

handoff

Show handoff status — tracked projects and install health.

rosehgal/handoff · 10 tokens

adr-review

Run the workflow in docs/playbooks/adr-review.md. You review only — never write or rewrite the ADR for me. Check problem framing, option fairness, trade-offs and consequences, reversibility, the revisit trigger, and weak reasoning. Give pointed questions and concrete suggestions; I write the words. If it supersedes an…

ahamedzoha/atelier · 0 tokens

milestone

Produce the next build doc. Run the workflow in docs/playbooks/milestone.md: read the active mode and current phase from PROJECT.md, find the next milestone in docs/progress.md, and write docs/milestones/ . - .md in the six-part format (Concept · ADR · Guided build · Challenges · Verify · Stretch). Respect the mode …

ahamedzoha/atelier · 0 tokens

mode

Run the workflow in docs/playbooks/mode.md: read the current mode from PROJECT.md, confirm the trade-off of the target mode in one line, update the Mode field and Current mode: line in PROJECT.md, and confirm the new rules. Modes: guided (I write all code), collab (split), autopilot (you write it and teach). Full…

ahamedzoha/atelier · 0 tokens

progress

Run the workflow in docs/playbooks/progress.md: read PROJECT.md, docs/progress.md, and the actual repo (trust the repo over the doc). Locate me, name concrete progress, append a dated session-log entry, propose the single next action, and check docs/learning-debt.md for anything worth pulling in. If I seem stuck…

ahamedzoha/atelier · 0 tokens

start

Turn this freshly cloned template into my project. Run the workflow in docs/playbooks/start.md: welcome me, run a short conversational interview (idea, background, goals, mode, stack, pace), then write PROJECT.md, the design skeleton, and the roadmap in docs/progress.md, and offer to write my first milestone. Keep it…

ahamedzoha/atelier · 0 tokens