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 agentmods add skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-helpnpx skills add ccarvalho-eng/codex-elixir-phoenix --skill elixir-phoenix-helpgit clone --depth 1 https://github.com/ccarvalho-eng/codex-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/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-help)<a href="https://agentmods.dev/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-help"><img src="https://agentmods.dev/badge/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-help.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.01205 |
| Opus 5 | $0.00012 | $0.00602 |
| Sonnet 5 | $0.00005 | $0.00241 |
| Haiku 4.5 | $0.00002 | $0.00120 |
Grade A, and why
elixir-phoenix-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 3d 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 — 103 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
`$elixir-phoenix-help` # Analyze context, suggest commands
`$elixir-phoenix-help` how do I debug this? # Route to `$elixir-phoenix-investigate`
`$elixir-phoenix-help` add a new feature # Route to `$elixir-phoenix-plan` -> `$elixir-phoenix-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
rg --fileson.codex/plans/*/plan.md— active work in progress? - Check git status: uncommitted changes? which files?
- Check for solution docs: use
rg --fileson.codex/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 | $elixir-phoenix-intro |
| Ideation | "explore", "brainstorm", "not sure", "how to approach", "vague idea" | $elixir-phoenix-brainstorm |
| New feature | "add", "build", "implement", multi-file | $elixir-phoenix-plan → $elixir-phoenix-work |
| Quick change | Single file, <50 lines, "fix typo" | $elixir-phoenix-quick |
| Bug | Error, stack trace, "broken", "failing" | $elixir-phoenix-investigate |
| Review | "check", "review", PR ready | $elixir-phoenix-review |
| Runtime durability | "race", "state machine", "retry semantics", "pause/resume", "restart safety", "durability", "Oban flow" | $elixir-phoenix-runtime-durability-review |
| Performance | "slow", "N+1", "memory" | $elixir-phoenix-perf, $elixir-phoenix-n1-check, $elixir-phoenix-assigns-audit |
| Research | "how to", "best practice", "evaluate lib" | $elixir-phoenix-research |
| Resume work | Existing plan with unchecked tasks | ``$elixir-phoenix-work --continue |
| Post-fix | "that worked", solved a hard bug | $elixir-phoenix-compound |
| Full cycle | Large feature, new domain area | $elixir-phoenix-full |
| Project health | "audit", "tech debt", "overall quality" | $elixir-phoenix-audit, $elixir-phoenix-techdebt |
| Deployment | "deploy", "release", "production" | $elixir-phoenix-verify then deploy skill |
| Permissions | "too many prompts", "allow", "permission fatigue" | $elixir-phoenix-permissions |
What ships with it
2 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.
- 3d ago First seen · 103 lines · 24 tokens per session scan A 09184dfe53a6
elixir-phoenix-help is a skill published in the GitHub repository ccarvalho-eng/codex-elixir-phoenix (11 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,205 once invoked, about $0.0001 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 skills, from other repositories
phoenix
Use when building an Elixir web app with Phoenix — contexts, Ecto schemas, changesets and migrations, LiveView, channels and PubSub, the generators, and the boundary between domain logic and the web layer. Covers the classic LiveView over-rendering and Ecto N+1 traps. NOT pure OTP work with no web or Ecto layer …
elixir-expert
Expert-level Elixir, Phoenix, OTP, and concurrent systems.
opik-backend
Java backend patterns for Opik. Use when working in apps/opik-backend, designing APIs, database operations, or services.
python-sdk
Python SDK patterns for Opik. Use when working in sdks/python, on SDK APIs, integrations, or message processing.
typescript-sdk
TypeScript SDK patterns for Opik. Use when working in sdks/typescript.
python-repl
Interactive Python REPL automation with common helpers and best practices.