The problem
I work across many repositories with four agent tools: Claude Code, Codex, GitHub Copilot, and Antigravity. Each project should give its agents its own set of skills, context, and MCP servers. In practice, those sets were copied by hand or installed for the whole machine. Over time they drift, get duplicated, and it gets hard to answer what a project's agent sees and where it came from.
AIKM starts from a hypothesis: declaring a project's agent environment once, in a neutral format, and generating each tool's native files is cheaper and more trustworthy than maintaining every tool's files by hand.
Catalog, manifest, and sync
Reusable pieces live in a catalog, which is a git repository of its own. Each project declares in aikm.yaml which pieces it uses and for which tools. aikm sync writes the files each tool reads and records in aikm.lock the catalog commit it used, the digest of each piece, and the files it now owns.
Each skill is written once to .agents/skills/, which Codex, Copilot, and Antigravity read. For Claude Code, .claude/skills/ points to that folder through a symlink. When one tool needs something different, a piece can carry a native version just for it.
Today the pieces are skills. Context (AGENTS.md and CLAUDE.md) and project MCP servers are the next kinds of piece.
visibility: public # public | private harnesses: [claude-code, codex, copilot, antigravity] pieces: [tdd, opinions, github]
External sources
A catalog skill can take its content from another git repository, pinned to a commit. sync fetches only the pieces the project declares and uses the content only when its digest matches the one recorded in the piece. Each source's commit goes into aikm.lock, and a second run reads from the cache, with no network.
For now, sources have to be readable without credentials, so only public repositories work.
Guarantees
sync fails closed. With invalid input, it exits without writing anything to the project and says what to do next. Every check runs before the first write.
A private piece never reaches a public repository. AIKM doesn't rely only on the visibility declared in the manifest: it asks GitHub, through gh, whether each of the project's remotes is private, and refuses if any isn't.
Besides aikm.lock, it only writes and deletes paths the lock says it owns. It doesn't run skill scripts and doesn't touch the tools' user settings. Running sync again with no changes produces no diff, so git diff shows exactly what it did.
AIKM repositoryOpen source soon
Updates
- AIKM now manages each project's agent environment, and the study was rewritten to cover the catalog, the manifest, sync, external sources, and the guarantees.
- First published.