A few months ago I wrote an article called [The First Thing I Install in Every Claude Code Project](https://eigenwise.io/writing/the-first-thing-i-install-in-every-claude-code-project) about codebase-mapper. That title is already out of date... quartermaster goes in first now, because it sets up codebase-mapper for me, builds the map, adds a starter set of live rules pulled from how I actually work, picks the stack plugins and permissions that fit the project, and asks before touching any of it. Then it stays there and keeps the whole Claude Code setup improving as the project changes.

You can drop it into an existing project too. It reads the actual session history and finds the missing stuff I'd probably never go looking for on my own: a capability I keep rebuilding by hand, a skill that's underperforming, a plugin from another marketplace, or something I installed months ago and never use.

Then every recommendation gets graded on the next round. It checks whether I used it and whether the thing it targeted got better, then says keep it, improve it or roll it back. If the last suggestion did nothing, it says so. That's the reason I trust it with the rest of the setup.

It's called quartermaster, it's in my Eigenwise Toolshed marketplace (mine, full disclosure, MIT, no signup or SaaS nonsense), and when it finds a gap it can:

* research a plugin from any marketplace on your machine or beyond it, check whether it's maintained and what people report about it, then give you the add and install commands
* connect an MCP server, build or improve a project-specific skill, add the missing project knowledge, or fix a scoped rule or permission
* turn off something you installed months ago and never actually use

Start a TypeScript monorepo and quartermaster can put in codebase-mapper, add live rules for the package boundaries, install the TypeScript tooling, build one command that runs the checks across every package, and seed the safe permissions you already approve elsewhere. A month later it might catch that releases are still five commands you run by hand and turn them into a project skill, or spot a plugin loading every session, throwing hook errors, and never showing up in the work, then offer to remove it. Put it in a research vault and it could build evidence rules and source-checking instead, with no code tooling at all.

The always-on part is a local hook that writes six counts when a session ends, no transcript text and no model call. Once enough work has piled up it offers you a round at the next pause, and if you say yes it reduces your last 30 days to a bounded summary (in one heavy-use month that's 127MB of JSONL going in and 31KB coming out) and brings the findings to you one at a time.

    /plugin marketplace add Eigenwise/eigenwise-toolshed
    /plugin install quartermaster@eigenwise-toolshed --scope project
    /quartermaster:setup

Then just work normally and say yes when it asks for a round. Install it per project so every setup stays specific to the work happening there.

Github: [https://github.com/Eigenwise/eigenwise-toolshed](https://github.com/Eigenwise/eigenwise-toolshed)  
  
I wrote up the whole loop and the reasoning behind it here: [https://eigenwise.io/writing/the-plugin-that-turns-claude-code-into-a-self-improving-monster](https://eigenwise.io/writing/the-plugin-that-turns-claude-code-into-a-self-improving-monster)

The First and Last Plugin You Should Ever Install in a Claude Code Project: Quartermaster, the Plugin That Turns Your Claude Code into a Continuously Self-Improving Machine