sync

sync is a command for coding agents from slash9494/ai-config-sync-manager. It costs 15 tokens per session (332 once invoked), scanned A, original, MIT.

A command for previewing or applying configuration synchronisation between Claude and Codex through AI Config Sync Manager.

In plain words
What is it for?
Use it to compare or synchronise agent settings, inspect planned file changes, review manual or partial-risk items, and apply approved updates with backups.
Why use it?
It shows a dry-run plan before changing files and requires confirmation before applying the plan, helping you review risks and avoid unexpected configuration changes.

Command

Part of the config-manager plugin — 1 skill, 5 commands shipped together

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/slash9494/ai-config-sync-manager/sync
Clone the repo
git clone --depth 1 https://github.com/slash9494/ai-config-sync-manager

Or install config-manager, the plugin that ships this one along with the rest of its 1 skill, 5 commands.

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/slash9494/ai-config-sync-manager/sync.svg)](https://agentmods.dev/commands/slash9494/ai-config-sync-manager/sync)
Your own site
<a href="https://agentmods.dev/commands/slash9494/ai-config-sync-manager/sync"><img src="https://agentmods.dev/badge/commands/slash9494/ai-config-sync-manager/sync.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 332 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.00015 $0.00332
Opus 5 $0.00008 $0.00166
Sonnet 5 $0.00003 $0.00066
Haiku 4.5 $0.00002 $0.00033

Measured 3d ago against content hash 0e25c92999c6, 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 3d 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.

integrations/claude-plugin/commands/sync.md · 29 lines

What it actually says

First run a sync plan:

!AI_CONFIG_SYNC_HOST=claude bash -lc 'case " $ARGUMENTS " in *" --apply "*) "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" sync '"$ARGUMENTS"' ;; *) "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" sync '"$ARGUMENTS"' --dry-run ;; esac'

Confirmation flow:

  • The slash command always shows a dry-run plan first.
  • After reviewing the plan, ask the user in chat whether to apply.
  • On the user's explicit yes, re-run this command with --apply.

Before applying changes:

  • Summarize the CLI output exactly; do not call a target an overwrite unless the CLI reports that the target exists.
  • Highlight manual and partial risk entries explicitly to the user before asking for approval.
  • Ensure backups are created automatically by the CLI on apply (Backup root: ... line).
  • Manual-risk entries are still plan candidates; --apply executes them after backups.

Apply only after the user explicitly confirms in chat:

AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" sync $ARGUMENTS --apply
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. 3d ago First seen · 29 lines · 15 tokens per session scan A 0e25c92999c6

Subscribe to this mod's changes

sync is a command published in the GitHub repository slash9494/ai-config-sync-manager (33 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 332 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-30.