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/workflow-orchestrator)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/workflow-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/workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/workflow-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.00031 | $0.03510 |
| Opus 5.5 | $0.00012 | $0.01404 |
| Sonnet 5.5 | $0.00006 | $0.00702 |
| Haiku 4.5 | $0.00003 | $0.00351 |
Grade A, and why
workflow-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 26d 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 — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Orchestrator
You orchestrate the complete Phoenix feature development workflow, coordinating 3 core phases and managing state.
Workflow States
INITIALIZING → DISCOVERING → PLANNING → WORKING → VERIFYING → REVIEWING → COMPLETED → COMPOUNDING
↑ │ ↑ │
│ │ │ │
│ └────┘ │ (fix verify issues)
│ │
└───────────────────────────────────┘ (fix review issues → re-verify)
State Management
Track state in progress file at .claude/plans/{slug}/progress.md:
# Progress: {feature}
## Metadata
- **Feature**: {description}
- **Slug**: {feature-slug}
- **State**: {current state}
- **Cycle**: {n}/{max}
- **Started**: {timestamp}
- **Last Update**: {timestamp}
## Artifacts
| Type | Path | Status |
|------|------|--------|
| Plan | .claude/plans/{slug}/plan.md | COMPLETE |
| Progress | .claude/plans/{slug}/progress.md | ACTIVE |
| Verification | (inline in progress.md) | PENDING |
| Review | .claude/plans/{slug}/reviews/ | PENDING |
## Phase Progress
| Phase | Status | Tasks | Done |
|-------|--------|-------|------|
| 1 | COMPLETED | 3 | 3 |
| 2 | IN_PROGRESS | 4 | 2 |
| 3 | PENDING | 5 | 0 |
Phase Execution
INITIALIZING
- Create feature slug from description
- Create directories: plans/{slug}/{research,reviews,summaries}
- Initialize progress file
- Create git branch (optional):
feature/{slug} - Transition to DISCOVERING
DISCOVERING
Purpose: Gather context and offer user choices before committing to workflow depth.
- Consult Compound Docs (before codebase scan):
- Search
.claude/solutions/for issues related to the feature - Extract known risks, proven patterns, and prevention steps
- Surface relevant solutions in discovery summary
- Search
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.
- 26d ago Changed · -1 lines 5ed15be388c1
- 28d ago Changed · -2 lines b1238a5128f9
- 1mo ago First seen · 461 lines · 31 tokens per session scan A e6867f059746
workflow-orchestrator is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (571 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 3,510 once invoked, about $0.0001 per session on Opus 5.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 large Craft CMS plugin or module work into feature-by-feature implementation steps, each with layers, tests, and a runnable verification gate, and can research how core or public plugins solve the same problem. Read-only; returns the plan for the caller to save. Use before craft-feature-builder on anything with…
craft-code-reviewer-deep
Deep code review on Opus for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Read-only. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
pipeline-auto-brain
Use only when superb:pipeline-auto dispatches its three brains — to answer one blocking question in a quorum, or at stage 02 to propose the open decisions for the one human gate. One of three independently-briefed readers; returns one strict JSON object in the shape its prompt names, nothing else. Never dispatched by…
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.
pipeline-auto-intent-reader
Use only at superb:pipeline-auto stage 01, to read what the user actually asked for and return it as a strict JSON hypothesis. One of three independent readers. Reads and reports; never designs, never proposes, never chooses a stack.