Tested plumbing, the marketplace's own checks, and a disposable Omarchy to test in.

The three parts are the Run and Store blocks a plugin copies into its own tree, the marketplace's own checks run locally, and repository suites run in a disposable guest. Behind the first are M13's 1,001 security blocker comments from one measured week: 587 raise a Run line, 527 a Store line, and runner plus store handle 777 of 1,001 when read as an upper bound, not as a result for any plugin (M13). No reviewer has seen a ported plugin yet.

What it delivers

| Command | What you get | Documentation | | --- | --- | --- | | omakit add <block> [<plugin-dir>] | Copy the Run or Store block into a plugin. The plugin owns the files, and an edited copy is never overwritten. | Blocks | | omakit inspect <plugin-dir> | See what the tree does and what deserves attention, with the file and line for each observation. | Inspect | | omakit verify <plugin-repo> | Get the marketplace's security result for your commit, exactly as it would see it. | Verify | | omakit submit <plugin-repo> | Run every submission check and get the issue title and body ready to paste. Nothing is posted. | Submit | | omakit watch ... | See whether the marketplace-validated commit is still current and what to do when it is not. | Watch | | omakit audit [<plugin>] | Find installed plugins running commits the marketplace never validated. | Audit | | omakit lab <command> | Set up, inspect, prove in or prune the disposable Omarchy guest. | Lab | | omakit weigh <plugin> | Measure a plugin's CPU and child processes against the shell's own baseline, then restore the shell config. | Weigh | | omakit setup, omakit doctor | Prepare or check the pin, completion, tools and disposable lab. | Install | | omakit pin, omakit upgrade, omakit parity, omakit help --agent | Maintain Omakit or inspect its own contract and parity proof. | All commands |

The complete syntax, options, exit codes and JSON/output contract are in the command reference.

Install

npm i -g omakit && omakit setup
npx skills add mtolhuys/omakit

Omakit needs Node 22+ and Git. omakit setup prepares the pinned marketplace checkout and shell completion. The blocks also need /usr/bin/python3. Audit and weigh need a running Omarchy shell. The lab needs KVM, QEMU and OVMF; omakit doctor reports what is missing and installs nothing.

Build

omakit add run <plugin-dir> and omakit add store <plugin-dir> copy versioned process and private-state plumbing into the plugin's omakit/ directory; the plugin owns those files, and an edited copy is never overwritten. Commit the copied files before checking, because check reads committed HEAD unless you pass --allow-dirty. Why that plumbing is worth taking from somewhere else is in one page.

Check

omakit inspect <plugin-dir> shows what the tree does, omakit verify <plugin-repo> runs the marketplace's baseline, and omakit submit <plugin-repo> runs every submission check and prints a title and body without posting them.

Track

omakit watch --all compares open submissions with the commits the marketplace validated, while omakit audit compares installed third-party plugins with their validated commits; both are read-only.

Prove

After one omakit lab setup, omakit lab prove <suite> boots a fresh overlay from the verified base, prints the guest identity, runs Run, Store or weigh in that guest, records the result, removes the overlay and checks the base unchanged.

omakit weigh <plugin> is the supporting desktop measurement: after explicit consent it restarts the shell without and with the plugin, reports CPU and child processes against the baseline's own spread, and restores shell.json.

Evidence

| What was measured | Record | | --- | --- | | Review plumbing | 1,001 blocker comments; Run 587, Store 527, either 777, M13 record | | Run | 19 of 19 on the desktop and 19 of 19 on the stock 4.0.3 guest at Run 0.2.1, desktop, fresh guest | | Store | 15 of 15 on the desktop and stock guest, including the simulated foreign owner, desktop, guest | | The disposable guest | guest omarchy 4.0.3-1, skew false, 2m 42.2s, 440,209,408 B overlay removed, base unchanged, fresh run | | The two ports | Theme Manager through Run, Sidecar through Store; neither submitted, no reviewer has seen either | | Validation drift | 326 of 519 readable open-submission comparisons stale, 64 of 583 unknown, dated record | | README captures | eight GIFs made from committed captures and scenes, with commands, hashes, dimensions and timings in the M10 record | | First-reader path | packaged install, blocks, checks, tracking and a 19-scenario guest run exercised from /tmp, dated record | | Package boundary | 0 runtime and 0 development dependencies in package.json; 0 marketplace writes enforced by the read-only tests |

Documentation

Every page, and which question each one answers: the documentation index.

• The path from a plugin to a listing and when a command stops
• Why the blocks exist, the blocks themselves and their design spike
• Commands, inspect, submit, watch, audit and weigh
• The disposable lab and every measurement
• Installation, media recipes and repository rules

Licence: MIT.