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/kaizengit clone --depth 1 https://github.com/littlebearapps/untetherWhat 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 | $0.00066 | $0.01662 |
| Opus 5 | $0.00033 | $0.00831 |
| Sonnet 5 | $0.00013 | $0.00332 |
| 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 yesterday.
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/*,hooks.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.
- yesterday First seen · 130 lines · 66 tokens per session scan A 0ea539f05525
kaizen is a command published in the GitHub repository littlebearapps/untether (66 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 1,662 once invoked, about $0.0003 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
remember
Consolidate stashes + friction into project memory.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
complete
Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag.
ace-learn
Learn from the latest completed task using ACE post-run feedback (gated; used by auto-hook and manual fallback).
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
learn
Force claude-smart to extract learnings from this session now.