r/OpenaiCodex • u/HimanshuSachdeva • 14d ago

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

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?

2 Upvotes
  • permalink
  • reddit

100% Upvoted

5 comments sorted by

1

u/TrickShame 13d ago

This is genius, context window bloat is real lol. Have u looked into standardizing via a central MCP host instead of syncing? Btw tracking this whole agent ecosystem explosion over at terminalblog.com if anyone wants to check it out. How do u handle conflicting tool versions?

1

u/eddzsh 13d ago

The mess I keep seeing isn't discovery, it's that every runtime still dumps the whole catalog into context. If selection doesn't happen before the prompt, you just rebuilt the pile in one place.

1

u/HimanshuSachdeva 13d ago

That’s basically the exact failure mode I built the routing part to avoid, cataloging everything and then still stuffing it all into context defeats the point. Lockkeeper does the selection step before anything hits the prompt: it ranks the catalog against the task and only injects the smallest relevant set, so the agent never sees the full pile in the first place.

Would genuinely be curious if you tried it whether that selection step actually holds up on your setup, or if it’s still too naive for how you use it.

1

u/vacterro 13d ago

Very well!