Borrowing it
Nothing to install: this file belongs to littlebearapps/untether. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/littlebearapps/untether/master/.claude/commands/kaizen.mdgit clone --depth 1 https://github.com/littlebearapps/untetherWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/littlebearapps/untether/kaizen)<a href="https://agentmods.dev/commands/littlebearapps/untether/kaizen"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/kaizen/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/littlebearapps/untether/kaizen"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/kaizen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00066 | $0.01664 |
| Opus 5.5 | $0.00026 | $0.00666 |
| Sonnet 5.5 | $0.00013 | $0.00333 |
| Haiku 4.5 | $0.00007 | $0.00166 |
Grade A, and why
kaizen scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 18d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are handling /kaizen. Always begin your output with the literal heading
## /kaizen (the Stop-hook and future runs detect a completed capture by that
marker — do not omit or reword it).
/kaizen captures process learnings — how the work went, not what the code
does — as durable bullets on a single permanent GitHub collector issue. It is
the cheap, high-frequency half; /kaizen-review is the weekly, human-gated
promotion half.
User input: $ARGUMENTS
Untether adaptations (read first)
Load .claude/rules/kaizen.md (the thin capture rule) and, for the full rubric,
docs/kaizen/README.md. Also .claude/rules/workflow-commands.md for the
cross-cutting rules. Key points:
- Authority: read-only except ONE
gh issue comment. Never edit code,.claude/rules/*,.claude/settings.json, orCLAUDE.md. Promotion to any of those is/kaizen-review's job, and even then only as a proposal. - Self-invokes at session end (a Stop-hook nudge is proposed to Nathan for wiring, but is not required — this command runs itself). Under Untether/cron it still self-invokes; the single collector comment is the one sanctioned autonomous external write in the suite (bounded, idempotent, one comment).
- Idempotent. Re-running must not duplicate a bullet already on the collector
this session. Resolve the collector by exact title with
--limit 200. - Redaction. Scrub tokens/keys/env/chat-content/fleet identifiers from every evidence ref before it lands in the comment.
What counts as a capture
A capture is a process learning with evidence, in one of these tag buckets (Untether-tuned):
[timing] [tooling] [issue-quality] [novel-pattern] [guardrail-block]
[engine-quirk] [cost] [meta]
Every bullet MUST carry:
- a tag from the list above,
- an evidence ref — a trace, a log signature, a
file:line, an issue#N, a PR#N, or an event signature (never vague "I noticed…"), - an S/C/R score — Severity
S0–S4/ Confidencelow|med|high/ Recurrence×N(seedocs/kaizen/README.mdfor the scales).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 18d ago Changed 8aeb31ced1ec
- 1mo ago First seen · 130 lines · 66 tokens per session scan A 0ea539f05525
kaizen is a command published in the GitHub repository littlebearapps/untether (74 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,664 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
voiceover
Start a feature the demo-driven way — approve the voice-over (instead of a PRD), build on a fresh worktree, ship a PR with the proof on it.
release
Run the iPolloWork release flow.
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.