Chapter 03 · The Versioned Layer

The Command Console

Every snippet below was probed against the CLIs installed on 2026-07-10 — 21 automated probes, 0 drift, 2 items verified by live evidence. This is the layer that rots; that's why it carries the stamps. A stale stamp means re-verify before trusting — the re-stamp protocol is at the bottom of this page.

Eggo the verification officer pressing a glowing stamp onto a floating command card while a rejected card slides into a disposal chute
stamp the card // chute the rot

Trust the stamp, not the memory.— why this page exists

Eggo leaning over a floating command card with a comically large magnifying glass, hugely enlarging its verification seal

C·01Terminal & Shell

verified 2026-07-10
claude -p "summarize this"          # print mode: respond and exit
claude -p --output-format stream-json --verbose | jq
claude -p --output-format json      # single JSON result

The agent as a Unix process — pipe it, wrap it, compose it. Formats: text (default), json, stream-json. --output-format only works with --print. Introduced in the first print-mode workshops (Aug 2025); syntax unchanged since.

changed 2026-07-10
claude --model opus | sonnet | haiku   # historical ladder
claude --model fable                   # current top alias

Aliases still resolve, but the ladder moved: fable (Claude Fable 5) now tops it. Any hardcoded model name is a dated sidebar, not doctrine — a rule this guide applies to itself, and this entry is its proof.

verified 2026-07-10
h() { claude --model haiku "$@"; }
alias opus='ENABLE_BACKGROUND_TASKS=1 claude --model opus'
popus(){ opus "$(pbpaste) --- $@"; }     # original workshop version
{ cat "$1"; echo "$2"; } | claude --print

All wrappers still defined in the live shell (funclist, funcwhere, funced too). Drift note: the live popus now composes dopus — clipboard-seeded prompts run permission-skipped. Audit your wrappers — they evolve when you aren't looking.

risky · verified 2026-07-10
claude --dangerously-skip-permissions        # YOLO mode
claude --allow-dangerously-skip-permissions  # newer: opt-in, not default-on

Both exist today. The second is the current recommendation when you must go this route: it enables bypassing without turning it on by default, and the CLI itself says "recommended only for sandboxes with no internet access." The framing stands: an explicitly risky mode requiring isolation and external verification — never a convenience default.

verified 2026-07-10
--allowedTools "Bash(bun init:*)"     # also: --allowed-tools
--append-system-prompt "..."
--settings 
--setting-sources ""

All four present and current. --setting-sources "" remains the nested-agent hook-recursion guard. --disallowedTools now exists as the deny-side counterpart.

verified 2026-07-10
codex exec "..."      # non-interactive Codex (alias: codex e)
zsh -lc 'echo ZDOTDIR=...'   # shell-discovery probes
whence -a 

Codex's print-mode equivalent, verified against the installed CLI. The zsh discovery probes are plain shell and don't rot.

C·02Context Packing & Search

verified 2026-07-10
ffg -y --template plan     # -y = copy to clipboard
ffg find  -y
ffg --list-templates

FileForge still installed and matching the original workshop syntax; templates are a maintained surface.

verified 2026-07-10
npx repomix@latest
repomix --token-count-tree --include "src/**" --compress --remove-comments

All four recorded flags present in current repomix.

verified 2026-07-10
packx --preview            # show matching files without packing
packx -i "*.ts" -x "*.test.ts" --diff --dirty --staged
packx --strip-comments --minify

All verified. --diff now means "files changed from main" — read it as a branch diff, not an unstaged diff (that's --dirty).

removed 2026-07-10
packx --skeleton           # gone from current packx

Not in current help. Nearest equivalents: packx --strip-comments --minify, or repomix --compress for structure-only extraction.

verified 2026-07-10
ghx "useSuspenseQuery repo:tanstack/query" -p   # GitHub code search → stdout

Still installed; -L caps result count. The Search-Editor curation flow it feeds is an editor feature and survives by construction.

C·03Hooks & Automation

verified live 2026-07-10
SessionStart       # identity / environment binding
UserPromptSubmit   # routing, skill injection
PreToolUse         # allow/deny gates
Stop               # proof enforcement

Verified the strongest way available: this guide was built inside a session running SessionStart, UserPromptSubmit, and Stop hooks — a Stop gate refused to let the work end before the guide existed. Hooks enforce; prose suggests.

verified 2026-07-10
npx claude-hooks           # scaffolding package, v2.4.0 on npm

Still published. For nested agents, pair hooks with --setting-sources "" to prevent recursion.

C·04Skills, Agents & Imps

verified 2026-07-10
/init                      # then review the generated CLAUDE.md
@import syntax             # modular guidance
progressive-disclosure skills

Current practice unchanged: keep global instructions thin, load specialized guidance only when relevant, test that a skill activates when intended, and put mandatory checks in hooks rather than hoping instructions are followed.

superseded 2026-07-10
imp -l                     # no standalone imp binary on PATH
imp --which "..."

The concept survives; the entry point moved. Imps now ship inside @johnlindquist/flows as flow-* commands with routing metadata in each imp's config. (The illustrations in this guide were generated by one: flow-eggo-pop-western.)

C·05Review, Verification & Spend

verified 2026-07-10
ccusage                    # daily/weekly/monthly/session/blocks
ccusage statusline         # compact line for Claude Code hooks

Still installed, grown a statusline mode. Spend visibility is necessary but not sufficient — budgets and parallelism cost policy remain your job.

durable practice
# the checklist that doesn't rot
- runnable verification script for repeated claims
- diff or latest commit reviewed from an independent context
- stable browser behavior → Playwright after repeated success
- wait for ALL council members; silence ≠ agreement
- persist the check: no saved check, no claim

These are practices, not flags — they verify by being done.

C·06Multi-Model & Browser Bridge

verified 2026-07-10
packx --preview            # always preview before sending context out
~/.oracle/sessions/{slug}/output.log   # read the saved result from disk

The session directory layout exists on disk exactly as recorded. The principle behind it: the bridge consults externally, but execution and proof stay local.

C·07Git & Isolation

durable · plain git
git add -p && git commit   # small commits, message preserves *why*
git worktree add ../lane-b feature-b   # disjoint parallel tracks
# commit BEFORE any autonomous interval

The durable layer needs no probing — it's plain git. One update since these lessons were first taught: per-agent throwaway worktrees are now a built-in feature of agent harnesses. The practice was ahead of the tools; keep the habit, enjoy the automation.

⟳Re-stamping protocol

  1. Run node scripts-field-guide-verify.mjs — every entry's probe re-executes against the live CLIs.
  2. If anything reports DRIFT, fix the guide entry first (update the snippet, move it to changed/superseded/removed).
  3. Run with --stamp to update last_verified — it refuses to re-date while drift exists.

The script and its data (field-guide/verification.json) live next to this site. The guide obeys its own prime directive: the stamp is a saved check, not a claim.

trust the stamp // not the memory