Agnostic Agent Router

Agnostic AI Agent Sync

Maintain a single unified folder of AI agent skills and instructions, making it seamless to switch between Antigravity, Claude, Codex, Cursor, Qoder, Windsurf, and others.

Dependency-free, with OS-level immutable symlinks — protected from being accidentally deleted or overwritten by aggressive IDE updates.

The Problem

Using multiple AI coding tools means your custom instructions end up scattered across `~/.cursorrules`, `~/.claude/skills/`, `~/.codex/config/`, etc. Updating one meant manually copy-pasting to all the others — and inevitably forgetting one.

Worse, existing sync approaches create regular symlinks that are **easily overwritten** by software updates, `git checkout` resets, or environment re-initialization. One bad update and your entire symlinked skill library vanishes.

**💡 Modern Alternative:** For users who prefer a protocol-level approach over file-system symlinks, check out [AutoVault](https://autovault.dev/). It provides a standardized way to manage and "serve" skills to different agents using the Model Context Protocol (MCP), though it requires Node.js and does not offer the OS-level immutable locking found in this project.

The Solution

**Agnostic AI Agent Sync** creates symlinks from each AI coding tool's config location to a single "Hub" folder you control, then **locks them at the OS level** so nothing can silently delete them (like a new `git clone` command for that slick new Skill).

Why This Is Different

Feature	Generic symlinks / npm tools	Agnostic AI Agent Sync
Survives app updates	❌ Silently deleted	✅ OS-level immutable lock
Maps .cursorrules ↔ CLAUDE.md	❌ Manual	✅ Automatic
Dry-run before changes	❌ YOLO	✅ Full analysis + confirmation
Clean skill repos	❌ Cloned repos pollute each other’s git state	✅ Each repo is an independent sibling
Dependencies	Node.js / npm	Zero — native bash & PowerShell
Undo / unlock	Manual googlin