chief-engineer

chief-engineer is a skill for Claude Code, Codex from himraven/codex-chief-engineer. It costs 100 tokens per session (2,756 once invoked), scanned A, original, MIT.

A coordination skill for leading complex software projects from architecture and task planning through evidence-based acceptance.

In plain words
What is it for?
Breaking down multi-workstream engineering, routing tasks to workers, preserving decisions between phases, and verifying their results.
Why use it?
It keeps key design decisions, responsibilities, risks, and quality checks with one accountable lead while assigning bounded work to other agents.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/himraven/codex-chief-engineer/chief-engineer
Any agent
npx skills add himraven/codex-chief-engineer --skill chief-engineer
Clone the repo
git clone --depth 1 https://github.com/himraven/codex-chief-engineer

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for chief-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/himraven/codex-chief-engineer/chief-engineer.svg)](https://agentmods.dev/skills/himraven/codex-chief-engineer/chief-engineer)
Your own site
<a href="https://agentmods.dev/skills/himraven/codex-chief-engineer/chief-engineer"><img src="https://agentmods.dev/badge/skills/himraven/codex-chief-engineer/chief-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,756 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00100 $0.02756
Opus 5 $0.00050 $0.01378
Sonnet 5 $0.00020 $0.00551
Haiku 4.5 $0.00010 $0.00276

Measured 4d ago against content hash 9390ebe56906, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

chief-engineer 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 4d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/ce-dispatch.sh, scripts/ce-token-report.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skill/chief-engineer/SKILL.md · 247 lines

How it starts

The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Chief Engineer

Manifesto

Sol is the architect, not the execution pool. Its output is design, decomposition, routing, and convergence—not every line of execution.

  • Do not spend chief context on routine execution.
  • Do not outsource architecture, contracts, red-line judgment, or acceptance.
  • Cut cost through less context replication and right-sized executors, never a weaker correctness gate.
  • Treat worker output as untrusted until its evidence is reproduced.
  • Never dispatch Sol as a worker. Use same-model children only for justified isolation or latency.

Sol holds decisions, not history. Persist decisions, contracts, and evidence before a phase expires.

1. Establish reality and design

  • Inspect actual files, Git state, logs, runtime behavior, and current documentation before accepting the premise.
  • Select the specialist skill before selecting the executor.
  • If the task is linear, do not invent phases or persistent workstreams.
  • Keep framing, architecture, contracts, ownership, state transitions, risk, topology, and acceptance criteria in the chief phase.
  • Use read-only scouts for bounded evidence gathering. Never delegate the decision that the evidence must support.

2. Model the lifecycle

Use three levels:

  • Objective — one durable outcome and one existing, user-approved chief-state for decisions, contracts, phase status, evidence, and next actions. Do not create a new state system.
  • Phase — one active chief decision context. Persist a handoff before replacement.
  • Workstream — one bounded ownership lane. Keep it persistent only for repeated exchanges or long-running state; otherwise use an ephemeral worker.

Use one chief context for small work, one or two sequential phases for medium work, and two to four for genuinely large work. Treat these as ranges.

Roll over at a natural research→implementation, implementation→integration, or module boundary. Elsewhere require lost facts, contradictory decisions, or repeated rereading. Compaction and high context are telemetry, not sufficient rollover reasons.

Read the full file on GitHub · 247 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 4d ago First seen · 247 lines · 100 tokens per session scan A 9390ebe56906

Subscribe to this mod's changes

chief-engineer is a skill published in the GitHub repository himraven/codex-chief-engineer (5 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 2,756 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

interview

Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.

Hmbown/CodeWhale · 40 tokens

local-frontend-check

Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.

ascending-llc/jarvis-registry · 52 tokens

ppt-review

Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.

Orkas-AI/Orkas · 2 tokens

agy-delegate

Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…

amElnagdy/delegate-skills · 132 tokens

helmor-debug-operate

Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…

dohooo/helmor · 117 tokens