What problem does it solve? Plugin authors and users have no reliable way to know how heavy an Omarchy Quattro plugin is on the shell. Declared timer intervals and source code say nothing about actual CPU usage or spawned child processes, and per-plugin memory inside the shell is only knowable through a controlled A/B measurement. ## Core Features & Use Cases - A/B shell measurement: Restarts the omarchy-shell without and with the plugin multiple times, measuring CPU deltas against a printed noise floor and counting child processes with their memory and CPU. - Consent-gated execution: Refuses to run without explicit agreement (exit 2, NOT WEIGHED), since each run restarts the user's bar, panels, and plugins; protects shell.json with a backup and verifies restoration via MD5 comparison. - README-ready evidence sentence: Prints a paste-ready sentence per plugin naming the CPU floor, child processes, Omarchy version, and measurement date, backed by a JSON evidence file. - Use Case: Before submitting a plugin to the marketplace, run omakit weigh my-plugin after the user agrees, then paste the produced sentence into the plugin's README under a "What it weighs" heading. ## Quick Start Ask the user for explicit permission to restart their shell several times, then run omakit weigh on the installed plugin and paste the resulting measurement sentence into its README.
