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.
npx skills add slash9494/ai-config-sync-manager --skill config-manager-statusgit clone --depth 1 https://github.com/slash9494/ai-config-sync-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-status)<a href="https://agentmods.dev/skills/slash9494/ai-config-sync-manager/config-manager-status"><img src="https://agentmods.dev/badge/skills/slash9494/ai-config-sync-manager/config-manager-status/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-status"><img src="https://agentmods.dev/badge/skills/slash9494/ai-config-sync-manager/config-manager-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.00527 |
| Opus 5 | $0.00009 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
config-manager-status 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 11d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Manager Status
Use this skill when the user asks for config sync status, host detection, or Claude/Codex drift.
Behavior
- If the user passes
-h/--help(or asks for usage/help), run... status --helpand print the CLI output as-is — do not execute the status report. - Resolve the bundled CLI from the Codex plugin root:
AI_CONFIG_SYNC_HOST=codex "$HOME/.agents/plugins/ai-config-sync-manager/bin/ai-config-sync" status. The launcher resolves the runtime viaAI_CONFIG_SYNC_ROOT(dev override) → PATHai-config-sync→npm execfallback. - Always export
AI_CONFIG_SYNC_HOST=codexbefore invoking the CLI from this skill so the default sync direction iscodex -> claude. - Default status checks both global and current project scopes.
- Use
--scope global,--scope project, or--scope allonly when the user asks to narrow the report. - Use
--include area[,area:item]and--exclude area[,area:item]when the user asks for a filtered diff. Item selectors are supported for itemized areas such asskills,permissions, andhooks. - Use
... status --jsononly when structured output is needed for follow-up automation. - Print the CLI output as-is for user-facing status. Do not rewrite it into a different summary format.
- The CLI may collapse 10+ item diffs per scope/area into counts such as
+12,-3,~10, or!2; when that happens, tell the user to open the printed detail file for the full item list and before/after previews. - Preserve the CLI's concrete item/source details when relaying status. Do not collapse items into vague phrases such as "content differs" or "missing skills" without the detail-file pointer.
- Do not infer sync state by editing or scanning config files directly when the CLI is available.
- If the bundled CLI is unavailable, report that the user must
npm install -g ai-config-sync-manager(or runnpm linkfrom the repo) and re-runconnect.
Safety
- Status is read-only.
- Highlight items marked
manual,partial, permissions, hooks, or custom commands as higher-risk apply targets. - Do not apply changes from a status command.
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.
- 11d ago First seen · 32 lines · 17 tokens per session scan A b4ed62474a32
config-manager-status is a skill published in the GitHub repository slash9494/ai-config-sync-manager (37 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 527 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…