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-briefnpx skills add ccarvalho-eng/codex-elixir-phoenix --skill elixir-phoenix-briefgit 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-brief)<a href="https://agentmods.dev/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-brief"><img src="https://agentmods.dev/badge/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-brief.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.00023 | $0.01083 |
| Opus 5 | $0.00012 | $0.00541 |
| Sonnet 5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade B, and why
elixir-phoenix-brief scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Use `rg --files` to find `.codex/plans/*/plan.md` and pick the most recent. How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Briefing
Interactive walkthrough of a plan's reasoning, decisions, and solution shape. Designed for developers who need to understand a plan in 1-2 minutes instead of reading the full document.
Why This Exists
Plans answer "what to do" but bury "why." This skill bridges that gap with an interactive walkthrough.
Usage
`elixir-phoenix-brief` # Latest plan
`elixir-phoenix-brief` .codex/plans/user-auth/plan.md # Specific plan
Arguments
$ARGUMENTS= Path to plan file (optional, auto-detects latest)
Mode Detection
Read the plan file and determine mode from phase statuses:
- All phases
[PENDING]= Pre-work briefing (what WILL happen) - Any phase
[COMPLETED]or[IN_PROGRESS]= Post-work briefing (what WAS done and why)
Execution Flow
Step 1: Locate and Load Plan
-
If
$ARGUMENTShas a path, use it -
Otherwise, find latest plan:
Use
rg --filesto find.codex/plans/*/plan.mdand pick the most recent. -
If no plan found, tell user and suggest
elixir-phoenix-plan -
Read the plan file
Step 2: Load Supporting Artifacts
Read what's available (don't fail if missing):
.codex/plans/{slug}/summaries/consolidated.md(research summary).codex/plans/{slug}/scratchpad.md(decisions, dead-ends).codex/plans/{slug}/progress.md(work log, post-work only)
Step 3: Present Briefing Sections
Present ONE section at a time, wrapped in the visual briefing block
(see references/briefing-guide.md Visual Formatting). After each
section, use ask the user directly with options:
- If sections remain: "Next: {title}", "Ask me a question about this", "Stop here"
- If final section: no question needed, show closing message
Section Flow (Pre-Work Mode)
| # | Title | Source |
|---|---|---|
| 1 | What We're Building | Summary + Scope |
| 2 | Key Decisions | Technical Decisions + scratchpad rationale |
| 3 | Solution Shape | Phases overview + Data Model |
| 4 | Risks & Confidence | Risks table + unknowns/spikes |
What ships with it
3 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.
- 5d ago First seen · 139 lines · 23 tokens per session scan B 563a0c363f6f
elixir-phoenix-brief is a skill published in the GitHub repository ccarvalho-eng/codex-elixir-phoenix (11 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,083 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…