Quick start
You need Node 22.18 or later. Nothing else: no build step, no dependencies.
git clone https://github.com/coo1white/yokotennode yokoten/bin/yokoten.ts install # once per computercd your-projectnode ~/.local/share/yokoten/bin/yokoten.ts init # once per project
Then open the project in Claude Code. It tells you which stage you are at, and the one next step.
Or paste this into Claude Code, in your project:
Read https://yokoten.app/agents.md and set yokoten up in this project.
agents.md is a short, plain list of steps. Your agent checks Node, installs yokoten, runs doctor, and asks you before it commits anything.
A one-command npx yokoten comes with the npm release.
Check it works
In your project, run doctor. It shows the whole road and marks the next step:
node .yokoten/bin/yokoten.ts doctoryokoten 0.1.0, self-test okthe road: stage 1 of 5, safety net 1. safety net done rules done tool-hook done commit-check done runtime next tests: CI does not run the tests; add a step that runs `npm test` … 2. issues and pull requests …
Shortened. Your steps will differ.
To see the guard stop something without running anything, hand it a pretend tool call:
echo '{"tool_name":"Bash","tool_input":{"command":"git push --tags"}}' | node .yokoten/bin/yokoten.ts hookyokoten: git push --tags pushes tags. Only the owner decides when to release. If the owner asked for this, they start the session with YOKOTEN_RELEASE_APPROVAL set.
Nothing is pushed: the hook only reads the call. Exit code 2 means “blocked”.