Adversarial fresh-context review of any non-trivial technical decision or code change. MUST be used before committing any change to smart contract code (xete-tab, Xete Swap), key handling (Black Knight), encryption logic (Xete Message, MCP server), or any irreversible/immutable deployment decision. Also trigger when…
Train and calibrate the gate system against a repo's real git history in an isolated sandbox. MUST be used when the user asks to backtest, replay, calibrate, or train the gates against history, and after installing gates into any repo with meaningful existing history. Uses real historical fixes as ground truth and…
Spec-first workflow for any feature or change expected to exceed one atomic commit, and for all work handed between Chef, Jo, or agent sessions. MUST be used when starting a new feature, refactor, or integration (House Elf features, MCP server changes, relay work, x402 extensions) — write the spec BEFORE any code.…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: