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.
git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenixWrote 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.
[](https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/planning-orchestrator)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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:
- Research files under
.claude/plans/{slug}/research/ - Compressed summary at
.claude/plans/{slug}/summaries/consolidated.md - 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.
-
mcp__tidewave__get_ecto_schemas→ pass to ecto-schema-designer -
mcp__tidewave__project_evalwith 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.
-
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:
- Discover: Glob
.claude/research/*.mdand.claude/plans/*/research/*.md - Relevance: Grep candidates for feature keywords — 2+ matches = relevant
- Freshness: Skip files older than 48h (
find -mtime -2) - 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). LogREUSED: {filename} (skipped {agent})in the scratchpad. - No match? Proceed normally.
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.
- 9d ago First seen · 233 lines · 62 tokens per session scan A 3a32c11a8d0d
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.
Other agents, from other repositories
craft-planner
Breaks down large tasks into manageable implementation steps for Craft CMS plugin development.
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.
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…
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.
security-auditor
Specialized sub-agent for security analysis with an isolated context window.
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.