its-over-9k

Guided first-install and reconfiguration flow for o9k. Use when the user invokes /o9k-init, on a fresh o9k install, or when the user wants to set up, reconfigure, or extend their companion stack. Detects what's installed, interviews the user (bundle, git, conflicts), resolves collisions with migration, then executes the setup.

Token usage report for the current project from Claude Code session transcripts. Use when the user asks how many tokens were used/saved, invokes /o9k-stats, or wants to verify the o9k pillars are paying off.

Meta-skill for the o9k doctrine and arbitration — who owns output style, the repo map, dispatch, memory, the plan. Load at session start, on conflicts between efficiency skills, and whenever unsure Path A vs Path B — if a team-up roster exists, external CLI tmux workers require team-up + dispatch mailbox/watcher (not bare dispatch). Also use when caveman vs other output-styles collide.

Personalized o9k orientation for the human. Use when the user invokes /o9k-guide, asks how o9k works or what they need to do, right after first-time setup, or when the SessionStart hook flags an unresolved arbitration. Explains what runs automatically, the few one-time actions left, and on-demand commands (/o9k-init, /o9k-stats, /o9k-update). Agent-only: if a team-up roster exists, external CLI spawns still require dispatch path B — this guide does not exempt that.

Check installed o9k pillars and companion frameworks for updates, and apply the safe ones. Use when the user invokes /o9k-update, asks whether anything is out of date, or acts on the SessionStart 'updates available' notice.

Cost-gated subagent dispatch for context isolation. Use for broad searches, lookups, log analysis, doc digestion, independent subtasks, OR whenever you spawn an external CLI worker via the team-up companion (planner/implementer/reviewer in tmux, cursor-agent/claude/codex/hermes). Path A = in-host RESULT subagents. Path B = mailbox run + team-up dispatch --run-id + cheap in-host watcher (runs wait) — REQUIRED for every external CLI tmux spawn when a team-up roster exists; bare dispatch without a watcher is an incomplete spawn (parent never gets notified).

Install a conflict-free stack of third-party o9k companion frameworks in one command. MUST use when the user asks to set up companions, install the recommended stack, add memory/docs/methodology/symbol tools alongside o9k, or extend an existing bundle — never hand-install MCP servers without checking arbitration first. Wraps install/o9k-companions.sh and enforces the one-owner-per-concern rule from using-o9k.

GitHub Scout for agent frameworks. MUST run before installing an unknown companion, extending a bundle, refreshing the o9k compatibility matrix, or answering 'what's new/better than X' for Claude Code plugins, MCP servers, or agent frameworks. Repeatable recon loop: hunt, score, classify against using-o9k arbitration, trial in sandbox, report — never dump raw search results into context.

Context-loading discipline for codebases. Use BEFORE opening, reading, or exploring files — and for monorepo/broad greps (TODO sweeps, 'where is X'): search first, read narrow, one repo map per session. Pair with dispatch path A when the sweep would pollute main context. Prevents the 20k-token 'let me look around' burn.

Memory-MCP integration for o9k. Use at session start (load the project briefing), when the user references past work ('the bug we had', 'where did we leave off'), before compaction or /clear (flush state), and when deciding what deserves persisting. Works with TIM (npm tim-cli) or hmem (npm hmem-mcp); hooks pick TIM when both are present.