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-upgradenpx skills add ccarvalho-eng/codex-elixir-phoenix --skill elixir-phoenix-upgradegit 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-upgrade)<a href="https://agentmods.dev/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-upgrade"><img src="https://agentmods.dev/badge/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-upgrade.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.00016 | $0.00314 |
| Opus 5 | $0.00008 | $0.00157 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
elixir-phoenix-upgrade 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.
What it actually says
Upgrade Workflow
Use when upgrading Elixir, OTP, Phoenix, Ecto, LiveView, or critical library dependencies.
Iron Laws
- Upgrade in small phases, not one giant jump.
- Read official migration guides before changing code.
- Separate dependency bump commits from behavior refactors.
- Deprecation warnings are treated as required follow-up.
- Keep a rollback point after each phase.
Upgrade Sequence
Step 1: Baseline
- Record current versions (
mix deps, runtime versions, lockfile state) - Run baseline verification (
mix compile, tests, lints) - Capture known failing checks before upgrades
Step 2: Plan Phases
Order upgrades from foundation to framework:
- Elixir/OTP runtime
- Core framework libs (Phoenix/Ecto/LiveView)
- Peripheral dependencies
Step 3: Execute Per Phase
For each phase:
- Update version constraints
- Refresh dependencies
- Apply required migration guide changes
- Run compile and targeted tests
- Commit if green
Step 4: Final Compatibility Pass
- Run full verification pipeline
- Address deprecations and behavior changes
- Confirm deployment/runtime config expectations
Output Expectations
Provide:
- Upgrade phase plan
- Breaking changes and required code adjustments
- Verification status by phase
- Remaining risks and rollback guidance
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 · 58 lines · 16 tokens per session scan A 0d55af5a4993
elixir-phoenix-upgrade is a skill published in the GitHub repository ccarvalho-eng/codex-elixir-phoenix (11 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 314 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
ash-framework
Use this skill working with Ash Framework or any of its extensions. Always consult this when making any domain changes, features or fixes.
phoenix-framework
Use this skill working with Phoenix Framework. Consult this when working with the web layer, controllers, views, liveviews etc.
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 …
code-review
Review code changes for regressions, correctness, and missing tests.
writing-review-packets
Create or revise Reviews packet markdown for a code diff, including section strategy, prose, hunk references, validation, and pushing packet revisions with the Reviews CLI. Use when the user asks to write a review packet, organize a diff for review, add prose around hunk refs, update a packet for a new patchset, or…
using-reviews-locally
Run and use the Reviews app locally, including server startup, port checks, local token setup, CLI config, pushing local reviews or new patchsets, and Codex workflow conventions. Use when the user asks to spin up Reviews, push a local review packet or revision, mint/access local API tokens, debug localhost review…