Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add slash9494/ai-config-sync-manager/plugin install config-managerWrote 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/skills/slash9494/ai-config-sync-manager/config-manager)<a href="https://agentmods.dev/skills/slash9494/ai-config-sync-manager/config-manager"><img src="https://agentmods.dev/badge/skills/slash9494/ai-config-sync-manager/config-manager/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/skills/slash9494/ai-config-sync-manager/config-manager"><img src="https://agentmods.dev/badge/skills/slash9494/ai-config-sync-manager/config-manager.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.00023 | $0.00407 |
| Opus 5 | $0.00012 | $0.00204 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
config-manager 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.
What it actually says
Config Manager
AI Config Sync Manager is an OSS workflow for keeping AI assistant configuration explicit, inspectable, and recoverable.
Rules
- Resolve the bundled CLI from the host plugin root:
${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync. The plugin's launcher resolves the runtime in this order:AI_CONFIG_SYNC_ROOT(dev override), PATHai-config-sync(npm install -gornpm link), thennpm execfallback. - Always export
AI_CONFIG_SYNC_HOST=claudebefore invoking the CLI from this skill so the default sync direction isclaude -> codex. - Prefer
--dry-runbefore any write. - Status checks both global and current project scopes by default.
- Print status CLI output as-is. Do not rewrite Codex and Claude status into different summary formats.
- If status prints a detail file path, point the user to that file for full item lists and before/after previews.
- Text sync for instructions and skills uses layered
rules/terminology-map.jsonand genericrules/host-target-templates.json; user/project overrides may add product-specific workflow vocabularies and host-specific target templates. - Manual review means show the diff and require explicit approval before apply.
- Verify backups before applying changes.
- Require manual confirmation before running commands that modify Claude configuration.
- Keep output focused on changed paths, skipped paths, and recovery steps.
Commands
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" status
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" connect
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" sync --from claude --to codex --dry-run
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 · 31 lines · 23 tokens per session scan A a94803e8cc9c
config-manager is a skill published in the GitHub repository slash9494/ai-config-sync-manager (37 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 407 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
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…