omen-tools

Blocks a firmware flash until an adversarial review of that change exists, using your parsed schematic as ground truth.

pipx install omen-tools
omen install

omen install finds the coding agents on your machine (Claude Code, Cursor, Codex), asks which to protect, wires the gate in, and then verifies it the way the client will actually call it — with a stripped PATH, because a hook the client cannot resolve fails open on two of three clients, and a gate that is silently off is worse than no gate at all.

What it does

Before a flash command runs, the gate asks whether a review exists for that exact source. If not, it starts one — locally, as a headless instance of the agent CLI you already have, so your firmware never leaves the machine — and denies the flash until the review lands. Findings cite the net, pin or line they rest on, checked against the netlist we parsed from your schematic.

Only a BLOCKER stops a flash. Builds are never blocked.

When it is in the way

/omen-skip-review        pause it for an hour
/omen-enable-review      turn it back on
OMEN_SKIP_VERIFY=1       skip one flash, even offline

Commands

omen install     wire the gate into your agents
omen doctor      check it is actually armed
omen uninstall   remove it

omen hook also exists; you never type it. It is what your agent's client runs before each shell command.