slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Connect Codex with the bundled open-source AI Config Sync Manager CLI.
Bidirectional sync for Claude Code and Codex — instructions, skills, agents, MCP servers, hooks, permissions.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Connect Codex with the bundled open-source AI Config Sync Manager CLI.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Paraphrase host-strict-vocab tokens (Claude-only in codex files, Codex-only in claude files) and register per-line overrides through the bundled open-source CLI so the result is masked from future status diffs.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Print the AI Config Sync Manager reference (commands, areas, risk levels, mapping qualities, action verbs, terminology layers, hidden markers, file locations) through the bundled open-source CLI.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Check AI Config Sync Manager status through the bundled open-source CLI.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Preview and apply AI config sync plans through the bundled open-source CLI.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Greets the user politely.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Triage stack traces and map them to likely source files.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Choose one external agent for bounded comparison work.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Review and adjust production UI with existing design conventions.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Diagnose cloud incidents from logs, metrics, and traces.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
A comprehensive verification system for Claude Code sessions.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Example manual fixture skill.
slash9494/ai-config-sync-manager
Skill Claude CodeCodex
Greets the user politely.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: