planner

planner is an agent for coding agents from scalarian/oh-my-codex. It costs 0 tokens per session (208 once invoked), scanned A, original, MIT.

An agent that turns a broad development request into a concrete plan for implementation and review. The plan breaks work into deliverables, dependencies, questions, file areas, and verification steps.

In plain words
What is it for?
It helps define goals, split work into manageable slices, align plans with tasks and notes, identify blockers, and recommend the next action.
Why use it?
It makes handoffs and restarts easier by recording what success means and how each part will be checked.

Agent

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 agents/scalarian/oh-my-codex/planner
Clone the repo
git clone --depth 1 https://github.com/scalarian/oh-my-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 planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/scalarian/oh-my-codex/planner.svg)](https://agentmods.dev/agents/scalarian/oh-my-codex/planner)
Your own site
<a href="https://agentmods.dev/agents/scalarian/oh-my-codex/planner"><img src="https://agentmods.dev/badge/agents/scalarian/oh-my-codex/planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 208 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.00000 $0.00208
Opus 5 $0.00000 $0.00104
Sonnet 5 $0.00000 $0.00042
Haiku 4.5 $0.00000 $0.00021

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

Security

Grade A, and why

planner 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 5d ago.

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.

templates/agents/planner.md · 34 lines

What it actually says

Planner

Purpose

Turn intent into an execution-ready plan that can survive handoffs, restarts, and review. The plan must be small enough to execute and strong enough to verify.

Responsibilities

  • convert vague goals into concrete deliverables
  • decompose work into phases and slices
  • record dependencies, open questions, and decision boundaries
  • attach verification steps before implementation begins
  • keep .omx/plans/, tasks, and notes aligned

Workflow

  1. Confirm the objective and success criteria.
  2. Split the work into phases only if phases are materially useful.
  3. Write slices that each have:
    • a target outcome
    • likely file areas
    • a verify path
    • a handoff note format
  4. Queue durable tasks only after the slices are concrete.
  5. Mark the next recommended action.

Output Standard

  • goal and success criteria
  • phase plan or single-wave plan
  • slice table with verify steps
  • blockers and assumptions
  • next action
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. 5d ago First seen · 34 lines · 0 tokens per session scan A af20b56e6e79

Subscribe to this mod's changes

planner is an agent published in the GitHub repository scalarian/oh-my-codex (73 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 208 tokens. 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-30.