№ 0077Skill
oh-my-musecode productivity layer
oh-my-musecode is a content bundle and CLI for Muse Code that installs 35 skills, slash commands, hooks, an MCP server and themes, with an ownership ledger so uninstall restores the machine byte for byte.
oh-my-musecode
omm is a curated content bundle, a thin CLI and a git marketplace for Meta Muse Code: thirty-five
skills, three slash commands, eight hooks, a reminder, an in-binary MCP server, three themes and four
settings profiles, installed through Muse's own plugin and config surface. Every byte it writes into
Muse's directories is recorded in an ownership ledger, so omm uninstall puts the machine back
byte for byte and omm doctor can tell you exactly which silent failure a live session would hit.
It never touches the Muse binary, never writes framework state into settings.json, and refuses to
write anything at all without a human (or an explicit --yes) in the loop.
Install
Phase one places one static binary and writes nothing else. Phase two (omm install) is the only
thing that touches Muse config (ARCHITECTURE R6).
curl -fsSL https://github.com/hypery11/oh-my-musecode/releases/latest/download/install.sh | sh
# options: --version <v> --dir <path> --modify-path --dry-run (OMM_VERSION, OMM_INSTALL_DIR)
Releases live on the releases page (scripts/release.sh
cuts them; the base is one variable at the top of install.sh, OMM_RELEASE_BASE_URL). Alternatively,
build from a clone:
git clone https://github.com/hypery11/oh-my-musecode && cd oh-my-musecode
cargo build --release -p omm && install -m 0755 target/release/omm ~/.local/bin/omm
omm install --source "$PWD" # a shipped binary must be told the checkout: --source or $OMM_SOURCE
omm must be on the PATH the host inherits: plugin hooks are declared as omm hook <name> and the
MCP server as omm mcp, and a command word that does not resolve never spawns, silently (doctor D15
is critical when that happens).
Upgrading from the 0.x plugin (Node CLI, Python hooks, role skills)? Read docs/MIGRATION.md first —
1.0.0 replaces that surface instead of extending it.
What omm install writes
The complete plan is built and validated before the first host mutation, then executed; a second run
is a no-op. The shape of the output (an earlier sandbox run; byte counts shift release to release):
$ omm install --source ~/src/omm
plan: 4 file(s) (32404 B), 3 settings key(s), 3 host mutation(s), trust /home/me/proj
marketplace omm: added (local-dir ~/src/omm)
plugin oh-my-musecode@omm: insta



ChatForm
Tgmlabs