planning-orchestrator

planning-orchestrator is an agent for Claude Code from oliver-kriska/claude-elixir-phoenix. It costs 62 tokens per session (2,200 once invoked), scanned A, original, MIT.

A research coordinator for Elixir and Phoenix feature planning. It asks several specialist agents to investigate the codebase, libraries, database schemas, OTP, and LiveView, then combines their findings.

In plain words
What is it for?
Use it when a Phoenix feature needs research from at least three areas, such as existing code patterns, library choices, database design, background processes, or LiveView screens.
Why use it?
It removes the need to repeat the same investigation across separate agents and gives the main planning process one concise research summary. It does not write the plan or ask the developer questions.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; mentions subagents; names the NotebookEdit tool.

Part of the phx plugin — 50 skills, 26 agents, 10 hooks shipped together

Good fit Use it when a Phoenix feature needs research from at least three areas, such as existing code patterns, library choices, database design, background processes, or LiveView screens.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator
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.

Clone the repo
git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix

Made for: Claude Code.

Or install phx, the plugin that ships this one along with the rest of its 50 skills, 26 agents, 10 hooks.

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 planning-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator/github.svg)](https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for planning-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,200 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00062 $0.02200
Opus 5 $0.00031 $0.01100
Sonnet 5 $0.00012 $0.00440
Haiku 4.5 $0.00006 $0.00220

Measured 9d ago against content hash 3a32c11a8d0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

planning-orchestrator 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 9d 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.

plugins/elixir-phoenix/agents/planning-orchestrator.md · 233 lines

How it starts

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

Planning Research Orchestrator

You run the RESEARCH portion of feature planning: fan out specialist agents in parallel, compress their output, and return a digest. The caller (/phx:plan on the main thread) owns everything interactive — clarifying questions, split decisions, plan writing, and the final STOP. You NEVER write a plan, never call AskUserQuestion, never talk to the user.

Your Contract

Input (from the spawning prompt): feature description, plan slug, and any pre-gathered context (Tidewave state, prior research paths).

Output:

  1. Research files under .claude/plans/{slug}/research/
  2. Compressed summary at .claude/plans/{slug}/summaries/consolidated.md
  3. A final message digest (≤500 words): key findings, decisions with rationale, contested decisions (options + per-agent stances, for the caller to present to the user), risks/unknowns, file paths.

Workflow

Phase 1: Runtime Context (Tidewave — when available)

Gather live project state before spawning. Skip if unavailable — agents fall back to static analysis.

  1. mcp__tidewave__get_ecto_schemas → pass to ecto-schema-designer

  2. mcp__tidewave__project_eval with route discovery:

    router = :code.all_loaded()
    |> Enum.find(fn {mod, _} -> function_exported?(mod, :__routes__, 0) end)
    |> elem(0)
    Phoenix.Router.routes(router) |> Enum.map(& {&1.verb, &1.path, &1.plug})
    

    Pass route list to phoenix-patterns-analyst.

  3. mcp__tidewave__get_logs level: :warning → include in research context

Phase 1b: Research Cache Reuse

Before spawning web/hex agents, check for prior research covering the feature's topics:

  1. Discover: Glob .claude/research/*.md and .claude/plans/*/research/*.md
  2. Relevance: Grep candidates for feature keywords — 2+ matches = relevant
  3. Freshness: Skip files older than 48h (find -mtime -2)
  4. Apply each relevant, fresh file: include findings in the digest, skip the corresponding agent (*-evaluation.md → hex-library-researcher, research-*.md → web-researcher for that topic). Log REUSED: {filename} (skipped {agent}) in the scratchpad.
  5. No match? Proceed normally.

Read the full file on GitHub · 233 lines

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. 9d ago First seen · 233 lines · 62 tokens per session scan A 3a32c11a8d0d

Subscribe to this mod's changes

planning-orchestrator is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (541 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 2,200 once invoked, about $0.0003 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-30.

Related

Other agents, from other repositories

craft-planner

Breaks down large tasks into manageable implementation steps for Craft CMS plugin development.

michtio/craftcms-claude-skills · 18 tokens

craft-code-reviewer-deep

Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.

michtio/craftcms-claude-skills · 62 tokens

architecture-discovery

Use when a product idea needs its technical decisions surfaced as questions before any of them are made — invoked by superb:craft once per session, after the idea is stated and before the first question round, for software projects whose stack is not yet decided. Returns candidate questions only; never chooses a stack…

kardebadas/claude-plugin · 68 tokens

bug-investigator

Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.

kardebadas/claude-plugin · 46 tokens

security-auditor

Specialized sub-agent for security analysis with an isolated context window.

KhaiTrang1995/claude-code-structure · 0 tokens

performance-engineer

Profiles systems, identifies bottlenecks, optimizes code and infrastructure, and prevents performance regressions. Uses flame graphs, benchmarking, and data-driven analysis. Use when optimizing performance, investigating slow operations, setting performance budgets, or analyzing benchmarks.

saitarrun/Sdlc-ai-workflow · 52 tokens