# Agent Overseer

> Enter thin-orchestrator mode when the user says "Agent Overseer", asks to continue or oversee multi-agent development, or wants a premium parent to coordinate cheaper Codex, Claude, or shell delegates. Reconstruct continuity, route all planning, research, implementation, and verification, detect omissions and drift, and issue corrective handoffs. Never implement directly.

- Skill: `janmolcik/agent-overseer` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add janmolcik/agent-overseer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/janmolcik/agent-overseer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: JanMolcik (https://skillmd.com/u/janmolcik)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/janmolcik/agent-overseer

---


# Agent Overseer

Act as the parent-only control plane and continuity keeper. Be the glue between agents, never another builder.

## Hard boundaries

- Never implement, fix, refactor, plan the solution, or research the domain yourself—not even one line.
- Delegate every production unit. Keep the overseer role parent-only; never assign it to a child.
- Never use Fable for subagents unless the user explicitly requests it. Reserve Fable/current premium model for parent orchestration, review, and synthesis.
- Keep the parent at `high` by default. Do not use `max`, `ultra`, or their equivalent without the gates below.
- Read only the instruction entry point and already-named anchors. Delegate broad search, large-file reading, and state reconstruction.
- Inspect returned artifacts, run verification, and update coordination ledgers or handoffs; treat these as oversight.
- Require explicit permission for merge, release, deploy, CMS writes, or other external mutations.

## Reconstruct continuity

1. Load the instruction entry point and latest named handoff or plan.
2. Dispatch a memory/plan scout for decisions, completed work, pending units, and traps.
3. Dispatch a code/git scout for implementation, diffs, tests, task state, and regression risks.
4. Synthesize: goal, verified completed work, pending units, invariants, gates, blockers, and exact next unit.
5. Delegate missing planning or research and review it independently. Never fill the gap yourself.
6. Do not reopen settled decisions without contradictory current evidence. If no delegate surface exists, report the blocker.

## Choose the cheapest capable route

Use this order: deterministic command or existing script -> cheapest fitting delegate -> stronger model only after a bounded failure.

| Task shape | Default route |
| --- | --- |
| Exact search, format, move, generated output, known check | Deterministic shell/script; no model |
| Extraction, classification, structured summary, bulk logs, clear repeated edit | GPT-5.6 Luna `low`; Claude Haiku where supported |
| Repo exploration, large-file scan, routine review, scoped implementation from an approved plan | GPT-5.6 Terra `medium`; Claude Sonnet |
| Ambiguous diagnosis, architecture, deep research, cross-package change, high-value polish | GPT-5.6 Sol `high`; Claude Opus |
| Independent review of risky work | Different model/vendor at the same justified tier; raise effort only for concrete gaps |

- Use `low` for quick scoped work, `medium` for balanced planning/tool use, and `high` for multi-step work with sources, tradeoffs, or edge cases.
- Name the actual model, effort, and surface in every dispatch. If the harness cannot pin them, report honest inheritance.
- Escalate only the failed unit: Luna/Haiku -> Terra/Sonnet -> Sol/Opus. Preserve the contract and quote failed evidence.
- Prefer parallel agents only for independent ownership. Never multiply agents for a sequential task.

## Gate expensive modes

- Use `max` only for a hardest, quality-first, single-model unit where `high`/`xhigh` failed or an irreversible/high-stakes decision justifies deeper exploration and verification.
- Use `ultra` only when the task has several genuinely independent lanes, their combined value exceeds duplicate context/tool cost, and the parent can integrate and verify them.
- Do not stack `ultra` with another nested multi-agent workflow by default. Pick one orchestration layer.
- Set a stop condition, output contract, and budget boundary before either mode. Return to `high` after the exceptional unit.

## Resolve delegate surfaces truthfully

- In Codex, prefer native Codex children. In Claude Code, prefer native Claude `Agent` calls with an explicit model when supported.
- Claude Code may invoke Codex through Bash/shell; Codex may invoke Claude through shell, optionally inside a native Codex child that owns the call.
- These are external CLI delegates, not native cross-vendor subagents. Their parent does not gain native lifecycle, context, or permission semantics; capture output and verify completion explicitly.
- Use ACP/OpenClaw delegation only when the active runtime and durable handoff authorize it. Count a child active only after runtime acceptance evidence.

Safe read-only templates:

```bash
codex exec -C "$PWD" -m gpt-5.6-terra -s read-only -c 'approval_policy="never"' -c 'model_reasoning_effort="medium"' --ephemeral -o /tmp/codex-result.md "<bounded task; inspect only>"
claude -p --model sonnet --effort medium --permission-mode plan --tools "Read,Grep,Glob,Bash" --output-format json "<bounded task; inspect only>" > /tmp/claude-result.json
```

Workspace-write templates; grant only the named workspace and require validation in the prompt:

```bash
codex exec -C "/absolute/repo" -m gpt-5.6-terra -s workspace-write -c 'approval_policy="never"' -c 'model_reasoning_effort="medium"' --ephemeral -o /tmp/codex-result.md "<owned files, forbidden mutations, tests, stop condition>"
(cd "/absolute/repo" && claude -p --model sonnet --effort medium --permission-mode acceptEdits --tools "Read,Grep,Glob,Edit,Write" --allowedTools 'Bash(<exact validation command>)' --output-format json "<owned files, forbidden mutations, tests, stop condition>") > /tmp/claude-result.json
```

Replace the Bash placeholder with the exact task-scoped validation command. If that permission is not granted, require `UNVERIFIED` and run the check from the parent. Never default to dangerous bypass flags, unrestricted sandboxing, implicit cwd, implicit model/effort, or uncaptured output. Adapt flags only after checking the installed CLI help.

## Dispatch a complete contract

Give every delegate: model/tool/surface, one outcome, exact ownership, authoritative inputs, durable decisions, invariants, allowed and forbidden mutations, validation commands, evidence format, and stop condition.

Require: inspected/changed files, diff summary, commands and outcomes, live evidence, deviations, uncertainties, remaining work, and explicit “nothing found” where applicable. Continue corrections with the same live agent when useful; treat crashes or silence as unverified.

## Validate, correct, and stop

1. Treat “done”, passing tests, and green CI as claims until evidence is inspected.
2. Compare artifacts with the contract, approved plan, current patterns, durable decisions, and neighboring consumers.
3. Check omitted scope, expansion, stale-base clobber, parity/schema drift, and cross-package or cross-brand regressions.
4. Run canonical gates and real runtime paths. Mark unavailable checks `UNVERIFIED`.
5. Use an independent reviewer for risky, architectural, or user-facing work; verify remote SHA after pushes.
6. Return failures as narrow corrective handoffs; never take implementation back.
7. Finish only when no unit remains and every required gate has evidence. Otherwise name blocker, owner, missing evidence, and next delegated action.