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-intronpx skills add ccarvalho-eng/codex-elixir-phoenix --skill elixir-phoenix-introgit 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-intro)<a href="https://agentmods.dev/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-intro"><img src="https://agentmods.dev/badge/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-intro.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.00020 | $0.00524 |
| Opus 5 | $0.00010 | $0.00262 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
elixir-phoenix-intro 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 4d 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
88% identical to intro — 17 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.
What it actually says
Plugin Introduction Tutorial
Interactive walkthrough of the Elixir/Phoenix plugin in 6 sections (~5 min).
Arguments
$ARGUMENTSmay contain--section Nto jump to a specific section (1-6)- No arguments = start from Section 1
Execution Flow
- Read
references/tutorial-content.mdfor all section content - Parse
$ARGUMENTSfor--section Nflag (1-6) - If
--section Nspecified, jump directly to that section - Otherwise start from Section 1
Section Presentation Loop
For each section:
- Present the section content completely — do NOT abbreviate or summarize. Every paragraph, table, and code block in the reference file must appear in output
- After presenting, use
ask the user directlywith options:- If sections remain: "Next: [next section title]", "Skip to Cheat Sheet", "Stop here"
- If on final section (6): no question needed, end with closing message
Section Titles
| N | Title |
|---|---|
| 1 | Welcome |
| 2 | Core Workflow Commands |
| 3 | Knowledge & Safety Net |
| 4 | Hooks & Behavioral Rules |
| 5 | Init, Review & Gaps |
| 6 | Cheat Sheet & Next Steps |
Iron Laws
- ONE section at a time — never dump all content at once
- User controls pace — always offer to stop between sections
- Clean formatting — use tables and code blocks, not walls of text
- NEVER skip the user's questions — tutorial is interactive, not a monologue; if the user asks a question mid-section, answer it before continuing
Closing Message
After Section 6 (or when user stops):
You're all set! Try ``elixir-phoenix-plan`` with your next feature to see the workflow in action.
Run ``elixir-phoenix-intro` --section N` anytime to revisit a specific section.
Notes
- This runs in main conversation context (not a subagent)
- Reference file is readable since skill runs in user's session
- Keep tone welcoming but concise — developers don't want fluff
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.
- 4d ago First seen · 65 lines · 20 tokens per session scan A d9c014e8c7f7
elixir-phoenix-intro is a skill published in the GitHub repository ccarvalho-eng/codex-elixir-phoenix (11 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 524 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to intro, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
playwright
Use when the task requires capturing or automating a real browser from the terminal.
agent-newbie-guide
Skill "agent-newbie-guide" from hashgraph-online/awesome-codex-plugins, covering codex 新手引导, 🚫 新手术语过滤(绝对禁止), 统一行为规范(内嵌), 📍 阶段位置 and 启动自检.
agent-learning-coach
中文学习教练技能。用于学习编程、英语、设计、产品、AI、数学或任何技能时,先诊断水平,再用讲解、练习、反馈、复习的循环推进。触发语包括"进入学习模式""我想学""带我练""帮我制定学习计划""像教练一样教我"。.
lab-creator
Guide for creating new AI Gateway labs. Use when users want to create a new lab in the labs/ folder. This skill provides the standard lab structure, templates, and patterns used across the AI Gateway repository including Jupyter notebooks, Bicep infrastructure templates, APIM policies, and README documentation.
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.