メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | o9k-stats |
| description | 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. |
Run the bundled analyzer against the current project:
node "${CLAUDE_PLUGIN_ROOT}/scripts/o9k-stats.mjs"
# different project dir: pass path as first argument
Present the output compactly (caveman rules apply). Interpretation guide:
caveman pulls (companion
upstream caveman; skip this line if it is not installed). Uncompressed
agents typically sit noticeably higher; falling share across sessions =
compression working.caveman (upstream reports ~65% measured output reduction).scout
discipline and whether something regenerates the repo map every turn.Limits (be honest about them): transcripts only cover Claude Code sessions on this machine; subagent traffic is attributed to its own transcript; there is no counterfactual baseline — for a before/after comparison, compare sessions from before the o9k install date with sessions after.