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.
npx skills add oliver-kriska/claude-elixir-phoenix --skill plangit 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/skills/oliver-kriska/claude-elixir-phoenix/plan)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/plan"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/plan/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/skills/oliver-kriska/claude-elixir-phoenix/plan"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.01636 |
| Opus 5.5 | $0.00017 | $0.00654 |
| Sonnet 5.5 | $0.00008 | $0.00327 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
plan 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 23d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Elixir/Phoenix Feature
Plan a feature by spawning Elixir specialist agents, then output structured plan with checkboxes.
What Makes /phx:plan Different from /plan
- Spawns Elixir specialist agents for research
- Plans with
[ecto],[liveview],[oban]task routing - Checks for Iron Law compliance in the plan
- Includes
mix compile/format/credo/testverification - Understands Phoenix context boundaries
Usage
/phx:plan Add user avatars with S3 upload
/phx:plan .claude/plans/notifications/reviews/notifications-review.md
/phx:plan Implement notifications --depth deep
/phx:plan .claude/plans/auth/plan.md --existing
Arguments
$ARGUMENTS= Feature description, review file, or existing plan--depth quick|standard|deep= Planning depth (auto-detected)--existing= Enhance an existing plan with deeper research
Workflow
- Gather context — File path (skip to agents), brainstorm interview.md (skip clarification), clear description, or vague
- Clarify if vague — Ask questions ONE at a time (skip if brainstorm interview.md exists with Status: COMPLETE)
- Detect depth — Auto-detect quick/standard/deep
- Runtime context (Tidewave) — Gather live schemas, routes, and warnings before spawning agents (direct path only — the research orchestrator gathers its own)
- Spawn research — Selective, based on need. 0–2 agents:
spawn directly in parallel. 3+ agents (broad multi-context feature):
determine the effective maximum nesting depth. Use an explicit positive-integer
CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTHvalue first; when it is unset, inspectclaude --version(the default is 1 in 2.1.217–2.1.218 and 3 in 2.1.219+). If the version is unavailable, conservatively use 1. At depth 3+, spawn ONEplanning-orchestratorto run and compress the fan-out. At depth 1 or 2, keep orchestration in this main session: spawn the selected specialist agents directly, wait for them, then spawnphx:context-supervisordirectly if compression is needed. Never spawn an orchestrator that cannot delegate. Read only the resulting digest andsummaries/consolidated.md. IfTaskCreateis in your tool list (never ToolSearch for it), create a task per spawn:TaskCreate({subject: "{Agent} research", activeForm: "Researching..."}), markin_progresson spawn,completedwhen done - Wait for ALL agents — Do NOT proceed until all return "completed". NEVER write plan while any agent is still running
- Breadboard (LiveView) — System map for multi-page features
- Completeness check — required when planning from review
- Split decision — One plan or multiple, concrete options
- Generate plan — Checkboxes, phased tasks, code patterns.
Also create
plans/{slug}/scratchpad.mdfor decisions and dead-ends - Self-check (deep only) — Three questions in Risks section
- Present and ask — STOP, show summary, let user decide
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago Changed · +1 lines d330943d7e29
- 1mo ago First seen · 152 lines · 42 tokens per session scan A 9326676a6f82
plan is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (569 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,636 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
standup
Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.
offboard
Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.
boss
Act as the boss — delegate the task to a free opencode agent, review its output, request revisions, and only after the user approves, supervise deployment end-to-end. Claude does not write code or do heavy implementation in this mode. Use when the user says "be the boss", "/claudeboss:boss", or wants Claude to manage…
odoo-task-completion
Use when wrapping up a project.task ticket — after writing the code, before claiming done. Orchestrates the code-review pass, the test-runner pass, and a customer-readiness check. Invoke instead of saying "I think it's done.".
odoo-task-completion
Use when wrapping up a project.task ticket — after writing the code, before claiming done. Orchestrates the code-review pass, the test-runner pass, and a customer-readiness check. Invoke instead of saying "I think it's done.".
manage-flows
Manage flow lifecycle - publish, test, batch operations, inventory reports. Use when the user asks to publish, test, batch manage, or get an inventory of flows.