Docs
muda is one binary and five skills. Install both, open a session in a GitHub repository, and the muda skill routes to the next step. For what the loop does, see the loop.
what you need
GH_TOKEN, then GITHUB_TOKEN, then your gh login. gh is not required when a token is set. Settings it cannot read are reported as unavailable.setup
$ curl -fsSL https://muda.tools/install.sh | sh
It downloads muda for your platform and verifies its checksum. muda update moves it to the latest release; muda version shows what you have.
$ muda skills install --agent claude --scope user
--agent is claude, pi or codex (default claude). --scope is user (default) or project. User scope writes to ~/.claude/skills, ~/.pi/agent/skills or ~/.codex/skills. Project scope writes to .claude/skills, .pi/skills or .agents/skills at the Git root. It refuses to overwrite skill files muda does not own.
In the repository, ask your agent to start delivery-waste work with muda. The muda skill checks the binary, checks it can read the repository, and asks before it creates the record. Then it routes to the next phase: measure, diagnose, fix or verify. Each phase stops at a checkpoint for your answer.
› use muda to find the delivery waste in this repo
commands
The skills run these. You can also run them yourself. muda help <command> prints the flags, and muda commands --json lists them all.
recipe reads one..muda/.what it writes
The read commands change nothing. muda record writes only .muda/, and needs no GitHub access. muda skills install is the one other write, and only when you ask for it. The agent commits record changes on a branch and opens a pull request for you to merge. Never edit .muda/ by hand.