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-helpgit 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-help)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/phx-help"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-help/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-help"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/phx-help.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.01176 |
| Opus 5 | $0.00031 | $0.00588 |
| Sonnet 5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
phx-help 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 5d 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.
This is a copy
94% identical to help — 57 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Help — Interactive Command Advisor
Helps users find the right command, skill, or agent for their situation.
Usage
phx-help # Analyze context, suggest commands
phx-help how do I debug this? # Route to phx-investigate
phx-help add a new feature # Route to phx-plan -> phx-work
Arguments
$ARGUMENTS— optional description of what the user wants to do- Empty = analyze current context (git status, existing plans, file patterns)
Execution Flow
Step 1: Gather Context
If $ARGUMENTS is non-empty, use it as primary signal.
Always gather ambient context (run in parallel):
- Check for existing plans: use Glob on
.claude/plans/*/plan.md— active work in progress? - Check git status: uncommitted changes? which files?
- Check for solution docs: use Glob on
.claude/solutions/**/*.md— prior knowledge?
Step 2: Classify Intent
Read references/tool-catalog.md for the full routing table.
Map the user's situation to one of these categories:
| Category | Signals | Primary Commands |
|---|---|---|
| Starting out | No plans, new to plugin | phx-intro |
| Ideation | "explore", "brainstorm", "not sure", "how to approach", "vague idea" | phx-brainstorm |
| New feature | "add", "build", "implement", multi-file | phx-plan → phx-work |
| Quick change | Single file, <50 lines, "fix typo" | phx-quick |
| Bug | Error, stack trace, "broken", "failing" | phx-investigate |
| Review | "check", "review", PR ready | phx-review |
| Performance | "slow", "N+1", "memory" | phx-perf, ecto-n1-check, lv-assigns |
| Research | "how to", "best practice", "evaluate lib" | phx-research |
| Resume work | Existing plan with unchecked tasks | phx-work --continue |
| Post-fix | "that worked", solved a hard bug | phx-compound |
| Full cycle | Large feature, new domain area | phx-full |
| Project health | "audit", "tech debt", "overall quality" | phx-audit, phx-techdebt |
| Dep update audit | "audit deps", "supply chain", "post-mix deps.update", "review mix.lock PR" |
phx-deps-audit |
| Manual dep vetting | "vet this package", "approve dep", "trust ledger", "after phx-deps-audit findings" | phx-deps-vet |
| Deployment | "deploy", "release", "production" | phx-verify then deploy skill |
| Permissions | "too many prompts", "allow", "permission fatigue" | phx-permissions |
| Returning after time off | "what did I miss", "back from vacation", "catch up", "what changed while I was out" | /catchup (companion plugin, separate install) |
What ships with it
1 file 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.
- 5d ago First seen · 106 lines · 62 tokens per session scan A 54241f4ca931
phx-help is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (541 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,176 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to help, differing in 57 lines, and is treated as a copy.
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,"…
teach
Teach the user a new skill or concept, within this workspace.