Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/littlebearapps/untether/kaizen-reviewgit 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-review)<a href="https://agentmods.dev/commands/littlebearapps/untether/kaizen-review"><img src="https://agentmods.dev/badge/commands/littlebearapps/untether/kaizen-review.svg" alt="Measured on agentmods" 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.00090 | $0.01436 |
| Opus 5 | $0.00045 | $0.00718 |
| Sonnet 5 | $0.00018 | $0.00287 |
| Haiku 4.5 | $0.00009 | $0.00144 |
Grade A, and why
kaizen-review 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 6d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are handling /kaizen-review — the weekly promotion pass over the process
learnings that /kaizen captured. It is propose-only and human-gated: it
recommends, drafts, and files proposals, but it never applies a change to any
authoritative surface itself.
User input: $ARGUMENTS
Untether adaptations (read first)
Load docs/kaizen/README.md (the full policy: gate, hierarchy, scales,
approval-boundary table) and .claude/rules/kaizen.md. Also
.claude/rules/workflow-commands.md. Key points:
- Authority: propose-only. NEVER auto-edit
.claude/rules/,hooks.json,CLAUDE.md, or code. The most it does to an authoritative file is draft a proposed diff into a non-authoritative location (incoming/kaizen-runs/, gitignored) and open a GH issue. Applying the draft is a later human//implementstep. - Two writes it MAY do: (1) strike a source bullet by editing the collector
comment (add
~~…~~+ a→ #NN/→ dismissed: reasonmarker); (2) open a GH issue for an accepted promotion. Both are confirm-gated under Untether-mode (state the recommended decision in text;AskUserQuestionreturns empty). - Idempotent. Re-running must not re-promote an already-struck bullet or
double-file an issue. Resolve the collector by exact title,
--limit 200.
The promotion gate
Promote a bullet (or a cluster) only if it clears the gate:
Recurrence ≥ 2 OR Severity ≥ S3 OR trivial-high-leverage OR explicit operator request.
Everything else defers (leave the bullet) or dismisses (strike with a reason).
The promotion hierarchy (cheapest sufficient artefact)
Pick the lowest rung that would actually prevent recurrence:
- pytest — a regression/guard test (best: makes the learning executable).
- doc — a line in an existing doc / reference / FAQ.
- rule-draft — a proposed edit to a
.claude/rules/*.md(drafted, never applied). - GH issue — when the fix is real work, file it (labelled, severity-tagged).
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.
- 6d ago First seen · 117 lines · 90 tokens per session scan A bef366de2112
kaizen-review is a command published in the GitHub repository littlebearapps/untether (66 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 1,436 once invoked, about $0.0005 per session on Opus 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
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
harness
Take one harness from "wired" to "the agent is visibly smarter for it".
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
refresh-compare-pages
Freshly research, add, and refresh marketing compare pages, then open a descriptive PR.
update-faq
could you please update DESIGNFAQ & DXFAQ based on the changes we are trying to achieve.
prp-plan
Create comprehensive feature implementation plan with codebase analysis and pattern extraction.