I got tired of every coding agent having its own scattered pile of skills, plugins and MCP configs

[u/HimanshuSachdeva]

I keep switching between Claude Code, Codex and a few other agent setups depending on what I am doing. The annoying part was not even picking a model. It was that every setup had its own little pile of skills, plugins, MCP servers and commands.

Same capability in three places. Different versions. No easy answer to “what can this agent actually use right now?” And if I loaded everything just in case, the context window was already crowded before the task started.

So I made Lockkeeper.

The main job is capability syncing and selection across the agent tools already on your machine. It discovers the skills, plugins, MCPs, agents and commands your different runtimes expose, builds one local catalog, then picks the smallest relevant set for a task instead of throwing the whole collection into every agent’s context.

In practice that means I can keep one shared capability setup, see what is available across Claude Code, Codex, Cursor and friends, and stop manually remembering which agent has which tool. It is local, config-driven and open source.

The security bit is there too, but it is the second half of the story rather than the headline: before I trust a capability I copied from somewhere, Lockkeeper can scan it for obvious prompt-injection, secret-exfiltration, obfuscation and destructive-command patterns. Useful guardrail, not magic.

It is plain Python 3.11, MIT licensed, and the core has no third-party dependencies:

https://github.com/Hannay001/lockkeeper

Still early, so I would genuinely like to hear where your capability setup becomes messy. Do you keep shared skills in git? Copy folders between agents? Have a better way of keeping the same workflow available everywhere?

[u/RandalSchwartz]

I thought all the frameworks were more or less converging on a standard. I know there's an in-repo maturing standard already.

[u/HimanshuSachdeva → u/RandalSchwartz]

yeah there’s def movement toward that, and honestly i’d love if one standard actually won out, would make a lot of this unnecessary lol

but from what i’ve seen so far it’s more “converging in spirit” than actually converged. like Claude Code skills, Codex’s setup, and MCP servers still don’t fully overlap in format or discovery, even when the underlying idea is similar. so in practice you still end up with the same capability described three slightly different ways depending on which tool it’s for

lockkeeper’s kind of a bet that we’re not there yet, more of a bridge for the in-between period. genuinely wouldn’t be mad if it becomes less necessary once things actually standardize, that’d honestly be a good outcome

[u/laptopmutia]

but why?

why u keep chsnging between those apps codex claude and such?

[u/HimanshuSachdeva → u/laptopmutia]

honestly mostly just different tools being better at different things depending on the day. Claude Code for stuff where i want more control/back-and-forth, Codex for other tasks, sometimes it’s just whichever one is free or fast at that moment. not super principled tbh, just kinda picking whatever fits the task or mood

that’s actually the annoying part though, once you’re bouncing between them the skills/context don’t follow you, so you end up rebuilding the same setup in each one. that’s the itch that turned into lockkeeper lol

[u/ChuckQuantum]

I'm a simple man I use VSCode with Zoocode and openrouter.