Open source
Give your agents genius-level protocol.
Plugins and mods for Claude Code that put the right model on each job, keep context small, and don't call work done until a check passes.
Claude Code without protocol is messy, costly and inaccurate. Subagents start on your most expensive model by accident, whole logs land in context, and work gets called done before anything checked it.
A written protocol fixes that. The suite goes one step further: wherever a rule can be a hook, a pinned agent, a workflow or a meter, it is one, so it doesn't depend on anyone remembering it.
The premise is that this makes inexpensive inference good. We haven't measured that yet; the proof page says what we have.
The ten rulesType these in Claude Code
/plugin marketplace add DojoGenesis/plugins
/plugin install dojo-suite@dojo-genesisdojo-suite installs all eight plugins. Or pick one at a time, e.g. /plugin install dojo-gates@dojo-genesis.
Classic hooks take effect once you run /reload-plugins and start a new session. Day one walks through it.
Mods are early access. Enable them with export CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 (or add it under env in ~/.claude/settings.json), then restart Claude Code. They load from dojo-router, dojo-meter and dojo-verify; dojo-suite includes all three, and if you installed plugins one at a time you need those three. Everything classic works without them.
Each lever names the hook, agent or workflow that does the work. Where a rule is still only prose, the method page says so.
dojo-router warns when a subagent or a workflow step would inherit your top model, and blocks it in block mode. Its mod fills in the model by role. dojo-protocol's four role agents are pinned: scout on haiku, builder and reviewer on sonnet, judge on opus.
dojo-gates refuses a whole-file read of a large file and points to grep or an offset and limit. The protocol adds the habit: grep first, and keep a small fix in the main thread.
dojo-flow's build workflow opens with a contract phase that writes the shared decisions and an ownership map, and it refuses tracks that overlap. Scouts run on haiku, builders on sonnet, judges on opus.
dojo-verify's Stop hook blocks a final message that claims success when no check has passed since your last edit. It never blocks twice in a row, so you can say plainly that it's unverified.
dojo-flow's scorecard reports dispatched, returned and failed, and only says verified when they match and the checks passed. dojo-verify's mod shows the same tally live.
dojo-gates refuses the command shapes that do damage you can't take back: blanket staging, rewriting commits that are already pushed, printing secrets, tokens inside URLs. For the rest, the protocol's rule is prose: check what will leave the machine, then get the go.
Classic plugins use ordinary hooks, agents and commands. Mods add live behavior through function hooks and are early access. dojo-suite installs all eight.
Ten rules at session start, and four role agents pinned to the right model.
Components, install, kill switchGuards that refuse blanket staging, rewrites of pushed commits, secret printing and oversized reads.
Components, install, kill switchWarns or blocks a dispatch that names no model. The mod routes it by role.
Components, install, kill switchA cost report from your transcripts, and a live band with the mod.
Components, install, kill switchBlocks a turn that claims success with no check behind it.
Components, install, kill switchParallel builds with a contract gate and a scorecard that counts returns.
Components, install, kill switchFinds broken hook interpreters, noisy injections and flags that are off.
Components, install, kill switchPre-registered experiments with with/without baselines.
Components, install, kill switchThe proof page lists what we've counted from the files on disk, with the method and the date, and says plainly what hasn't been measured yet, including whether any of this lowers cost or raises accuracy.
ProofThe promise
Genius is one protocol away.
Protocol and inexpensive inference go together. Claude Code without protocol is messy, costly and inaccurate; with it, each job gets the smallest model that can do it, a small context, and a check before anyone says done.
Rules that live in prose fade. So wherever a rule can be a mechanism, it is.
The dojo is not the building. The dojo is the practice.