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 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/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/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="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.00023 | $0.01083 |
| Opus 5.5 | $0.00009 | $0.00433 |
| Sonnet 5.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 1mo 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.
- 1mo 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 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,083 once invoked, about $0.0001 per session on Opus 5.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
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. Use when the user mentions Phoenix, OTP, Erlang, concurrent, or functional, or when the task involves Elixir Fundamentals or Phoenix Framework.
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.
langbot-eba-adapter-dev
Build, refactor, and test LangBot platform adapters for the Event-Based Agents architecture. Use when adding or migrating Telegram, Discord, or other messaging platform adapters to the EBA adapter layout, validating unified event/message conversion, writing live adapter probes, or using standalone plugin runtime plus…
langbot-dev
Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…