senior-mode

Delegates repository investigation and code review to Codex CLI while the session model handles judgment.

15|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/NewTurn2017/fable-senior-mode --skill senior-mode-newturn2017
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-mode
Source: https://github.com/NewTurn2017/fable-senior-mode
Command: npx skills add https://github.com/NewTurn2017/fable-senior-mode --skill senior-mode-newturn2017

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? High-reasoning models waste expensive tokens on mechanical work like reading repositories, gathering evidence, and running review passes. This Skill reserves the session model for senior judgment—deciding what to investigate, writing delegation prompts, and judging tradeoffs—while routing the legwork to cheaper delegates like Codex CLI, DeepSeek via OpenRouter, or Opus subagents. ## Core Features & Use Cases - Companion-script delegation: All Codex calls go through a dependency-free Node.js script that runs tasks in foreground or background, tracks job state on disk, and supports wait, watch, status, result, and cancel commands. - Tiered delegate routing: Choose Heavy (sol, high effort), Light (luna, max effort), or Light+wide (DeepSeek via OpenRouter with 1M context) based on whether the work feeds hard-to-reverse decisions or bulk evidence gathering. - Multiple delegation paths: Pin sessions to Codex, Luna, DeepSeek, an Opus single agent, or an Anthropic agent team via slash commands like /senior-mode:codex and /senior-mode:team. - Use Case: Facing a multi-file migration, you invoke /senior-mode, and Claude writes a bounded investigation prompt, delegates the repo scan to Codex in the background, reads the returned evidence report, and produces a decision document—without ever reading the codebase itself. ## Quick Start Type /senior-mode in Claude Code with a description of the architectural or debugging question you need investigated, and Claude will delegate the evidence gathering to Codex and return a senior judgment.

Frequently Asked Questions about senior-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate code investigation to Codex from Claude Code?

Invoke /senior-mode in Claude Code and describe the decision you need. Claude writes a bounded delegation prompt and runs it through the codex-companion.mjs script using task --wait --read-only, returning an evidence report for judgment.

What is the difference between /senior-mode:codex, :luna, and :deepseek?

All three use the same companion script but pin different models. The codex path uses the default Codex model, luna pins gpt-5.6-luna at max effort, and deepseek routes through OpenRouter to DeepSeek V4 Flash with a 1M context for wide scans.

Does senior-mode work without the Codex CLI installed?

No, the default delegation paths require an installed and authenticated Codex CLI since the companion script shells out to the codex binary. The Opus single-agent and Anthropic team paths use Claude Code's native Agent tool instead.

How do I track a background Codex job in senior-mode?

Every background task returns a job id. Use the companion script's status, wait, watch, result, or cancel commands with that job id; job state is stored under .senior-mode/codex/jobs/ in the workspace root.

When should I not use senior-mode?

Skip it for small tasks, single-file edits, obvious bug fixes, or any work where Claude would simply write the code directly. The skill is explicit-invocation only and is designed for judgment-heavy work, not routine implementation.

Can Codex delegates run browser-based QA or screenshots?

No, Codex runs sandboxed without an attachable browser or CDP endpoint, so Chrome-driven QA fails there. Browser verification stays with the orchestrator using the browser-use skill, while delegates handle code paths and test runs.