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 phx-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/phx-plan)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/phx-plan"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-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/phx-plan"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-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.00044 | $0.01399 |
| Opus 5 | $0.00022 | $0.00700 |
| Sonnet 5 | $0.00009 | $0.00280 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
phx-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 6d 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 — 146 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 researching the relevant Elixir/Phoenix concerns, then output a structured plan with checkboxes.
What Makes phx-plan Different from /plan
- Covers relevant concerns through resumable research tracks
- 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
- Text after the skill name = 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 research), 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
- Create research state — Before research, create
.claude/plans/{slug}/scratchpad.mdwith a concern-track checklist - Gather optional runtime context — Only when Tidewave tools are independently configured and exposed; otherwise inspect source, routes, schemas, and tests
- Research selectively — Cover only relevant concerns. Native generic
subagents may run independent tracks in parallel, but they are optional.
Without them, run every selected track sequentially in this session and
save evidence under
.claude/plans/{slug}/research/ - Finish ALL research tracks — Maintain the scratchpad checklist,
marking each selected track
[x]only after its evidence is captured. NEVER write the plan while any selected track remains unchecked - Breadboard (LiveView) — Produce the system map from collected evidence
- Completeness check — MANDATORY when planning from review
- Split decision — One plan or multiple, concrete options
- Generate plan — Checkboxes, phased tasks, code patterns.
Reuse
.claude/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.
- 6d ago First seen · 146 lines · 44 tokens per session scan A 1847c13ef5c1
phx-plan is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (542 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 1,399 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
craft-php-guidelines
Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers…
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
milp-modeling-gurobi
When the user wants to build, solve, and debug mixed-integer linear programs in Python with Gurobi — creating variables, writing constraint-builder functions, setting objectives and parameters, handling solver status, and extracting solutions safely. Also use when the user mentions "gurobipy," "build a MIP model,"…
numpy-vectorization-for-optimization
When the user wants to remove slow Python loops from metaheuristic or optimization code using NumPy — population-level operations, batch fitness evaluation, distance matrices, broadcasting, argsort/argpartition idioms, defaultrng, and memory layout. Also use when the user mentions "vectorize," "numpy broadcasting,"…
odoo-js
Use when writing, reviewing, or migrating any JavaScript, OWL component, QWeb/OWL template, or SCSS under static/src in an Odoo module — POS overrides, backend widgets, website/public widgets, services. Carries PSAE review-derived principles for OWL correctness, the patch() discipline, template conventions, frontend…