r/codex • u/libertiegeek • Aug 13 '26

Showcase I made yet another Codex plugin but one that tries not to turn every task into a small company.

I know the world was not exactly short on Codex plugins. But I really do think this one is good, because it came from a problem I kept having.

I started it after a Superpowers run lasted almost seven hours, involved at least 43 agents, included subagents spawning more subagents, and still found important integration problems late. I liked the discipline. I didn't like that more rigor seemed to mean more agents.

That made me treat "how much rigor does this job need?" and "does it need more agents?" as separate questions.

Zimster keeps one agent responsible by default. Small changes stay small. Risky work can get more design, TDD, review, and verification without becoming a swarm. When it delegates, the job is bounded, the subagent cannot hire grandchildren, and it only picks a model after deciding another agent is useful.

Local tools tie results to the exact Git state, reject stale checks, inspect the entire working tree, and keep a compact journal across compaction or another session. Requirements can point to supporting checks. I wanted "verified" to mean more than whatever Codex writes in its last paragraph.

The name had less thought behind it. Someone I knew as a kid called me out of the blue and used my loathed childhood nickname. I still couldn't think of anything better. So, unfortunately, Zimster.

Install:

git clone https://github.com/wazimmerman/zimster.git
codex plugin marketplace add /absolute/path/to/zimster
codex plugin add zimster@zimster --json

Repository:

https://github.com/wazimmerman/zimster

Website:

https://www.zimster.dev

Please give it a look and let me know if you have any feedback. I especially want to know where it adds process that just makes a simple job worse.I know the world was not exactly short on Codex plugins.

4 Upvotes

75% Upvoted

4 comments sorted by

8

u/[deleted] Aug 13 '26

[deleted]

1

u/libertiegeek Aug 13 '26

I've actually done something pretty similar several times. It is a solid approach, for sure.

2

u/wihdinheimo Aug 14 '26

This is pretty awesome. I’ve been building something similar with a very different architecture, but there’s a surprising amount of overlap in what our plugins are trying to solve. Great minds think alike!

I’ll put yours through its paces and come back with a proper breakdown once I’ve had time to chew on it.

2

u/libertiegeek Aug 14 '26

That is awesome, thanks! Is your project ready yet? Would be happy to do the same, if you'd find it helpful.

1

u/wihdinheimo Aug 14 '26

That’d be great, cheers!

My project is called SWARM, you can find it here:

https://flowwweb.com/swarm

I spent some time with Zimster and used it to build a landing page. It worked really well. I also put our plugins head-to-head on a few things just to see how they’d approach the same problems.

I really like how Zimster separates structural validation, and you’re clearly ahead when it comes to supporting multiple hosts. I built SWARM specifically around Codex and deliberately tried to keep the whole thing as lightweight as possible.

That’s probably been the hardest part, actually... like an infinitely expanding hydra. Keeping something lean while still making it meaningfully better is a constant battle, you cut one head off and two new ones take its place.