What is config-manager-sync?

A command-line tool for previewing and applying configuration synchronisation between Codex and Claude, two AI coding assistants. It can sync global settings, project settings, or both.

Use it to compare and synchronise shared AI configuration, choose a sync direction, and limit the work to global or project settings.

It lets you inspect proposed configuration changes before applying them, reducing the risk of changing settings unexpectedly. By default, it previews changes from Codex to Claude.

config-manager-sync — Skill for Claude Code and Codex by slash9494

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.

Any agent

npx skills add slash9494/ai-config-sync-manager --skill config-manager-sync

Clone the repo

git clone --depth 1 https://github.com/slash9494/ai-config-sync-manager

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/slash9494/ai-config-sync-manager/config-manager-sync/github.svg)](https://agentmods.dev/skills/slash9494/ai-config-sync-manager/config-manager-sync)

Your own site

<a href="https://agentmods.dev/skills/slash9494/ai-config-sync-manager/config-manager-sync"><img src="https://agentmods.dev/badge/skills/slash9494/ai-config-sync-manager/config-manager-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/slash9494/ai-config-sync-manager/config-manager-sync"><img src="https://agentmods.dev/badge/skills/slash9494/ai-config-sync-manager/config-manager-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 704 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.00704
Opus 5	$0.00009	$0.00352
Sonnet 5	$0.00004	$0.00141
Haiku 4.5	$0.00002	$0.00070

Measured 9d ago against content hash dd847ed71922, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

config-manager-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 9d 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/codex-plugin/skills/config-manager-sync/SKILL.md · 44 lines

How it starts

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

Config Manager Sync

Use this skill when the user asks to sync Codex and Claude configuration with AI Config Sync Manager.

Behavior

If the user passes -h / --help (or asks for usage/help), run ... sync --help and print the CLI output as-is — do not run a dry-run or apply.
Resolve the bundled CLI from the Codex plugin root: "$HOME/.agents/plugins/ai-config-sync-manager/bin/ai-config-sync". The launcher resolves the runtime via AI_CONFIG_SYNC_ROOT (dev override) → PATH ai-config-sync → npm exec fallback.
Always export AI_CONFIG_SYNC_HOST=codex before invoking the CLI from this skill so the default sync direction is codex -> claude.
Default to dry-run: AI_CONFIG_SYNC_HOST=codex "$HOME/.agents/plugins/ai-config-sync-manager/bin/ai-config-sync" sync --dry-run.
Default sync scope is global and project when --scope is omitted.
Use --scope global, --scope project, or --scope all to narrow or make the sync scope explicit.
For explicit direction, pass the requested hosts, for example AI_CONFIG_SYNC_HOST=codex "$HOME/.agents/plugins/ai-config-sync-manager/bin/ai-config-sync" sync --from claude --to codex --dry-run. Explicit --from/--to overrides the env-based default.
For partial sync, pass selectors with --include area[,area:item] and --exclude area[,area:item]. Include is applied first, exclude is applied last. Item selectors are supported for itemized areas such as skills, permissions, and hooks.
Text sync for instructions and skills uses rules/terminology-map.json for layered terms/model names and rules/host-target-templates.json for generic host surfaces. Product/workflow-specific vocabularies should be supplied through project-level overrides under rules/.
Manual-risk entries are still sync plan candidates. Treat partial and manual entries as higher-risk entries that must be clearly shown in the dry-run.
If the bundled CLI is unavailable, report that the user must npm install -g ai-config-sync-manager (or run npm link from the repo) and re-run connect.

Read the full file on GitHub · 44 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.

9d ago First seen · 44 lines · 18 tokens per session scan A dd847ed71922

Subscribe to this mod's changes

config-manager-sync is a skill published in the GitHub repository slash9494/ai-config-sync-manager (37 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 704 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.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens