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 georgeguimaraes/claude-code-elixir --skill using-elixir-skillsgit clone --depth 1 https://github.com/georgeguimaraes/claude-code-elixirWrote 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/georgeguimaraes/claude-code-elixir/using-elixir-skills)<a href="https://agentmods.dev/skills/georgeguimaraes/claude-code-elixir/using-elixir-skills"><img src="https://agentmods.dev/badge/skills/georgeguimaraes/claude-code-elixir/using-elixir-skills/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/georgeguimaraes/claude-code-elixir/using-elixir-skills"><img src="https://agentmods.dev/badge/skills/georgeguimaraes/claude-code-elixir/using-elixir-skills.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.00096 | $0.00549 |
| Opus 5.5 | $0.00038 | $0.00220 |
| Sonnet 5.5 | $0.00019 | $0.00110 |
| Haiku 4.5 | $0.00010 | $0.00055 |
Grade A, and why
using-elixir-skills 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 2mo 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
THIS IS NOT OPTIONAL. Skills tell you HOW to explore and WHAT to look for. You cannot rationalize your way out of this.
The Rule
Elixir/Phoenix/OTP task → Invoke skill FIRST → Then explore/research → Then write code
Skills come before exploration. The skills tell you what patterns to look for, what questions to ask, and what anti-patterns to avoid. Exploring without the skill means you don't know what you're looking for.
Skill Triggers
| Trigger Phrases | Skill to Invoke |
|---|---|
| code, implement, write, design, architecture, structure, pattern | elixir-thinking |
| LiveView, Plug, PubSub, mount, channel, socket, component | phoenix-thinking |
| context, schema, Ecto, changeset, preload, Repo, migration | ecto-thinking |
| GenServer, supervisor, Task, ETS, bottleneck, Broadway | otp-thinking |
| Oban, workflow, job queue, cascade, graft, background job, async job | oban-thinking |
Red Flags
These thoughts mean STOP—invoke the skill:
| Thought | Reality |
|---|---|
| "Let me explore the codebase first" | Skills tell you WHAT to look for. Invoke first. |
| "Let me understand the code first" | Skills guide understanding. Invoke first. |
| "But first, let me..." | No. Skills come first. Always. |
| "I'll add a process to organize this" | Processes are for runtime, not organization. |
| "GenServer is the Elixir way" | GenServer is a bottleneck by design. |
| "I'll query in mount" | mount is called twice. |
| "Task.async is simpler" | Use Task.Supervisor in production. |
| "I know Elixir well enough" | These skills contain paradigm shifts. Invoke them. |
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.
- 2mo ago First seen · 44 lines · 96 tokens per session scan A cafc4a266396
using-elixir-skills is a skill published in the GitHub repository georgeguimaraes/claude-code-elixir (168 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 96 tokens to every session and 549 once invoked, about $0.0004 per session on Opus 5.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
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.
Elixir Patterns
Use this skill when working on Elixir/Phoenix projects and you want maintainable OTP-friendly structure, clear boundaries, and robust error handling.
tree-sitter-language-pack-extracting-code-structure
Use when the user wants structured code metadata from a source file — functions, classes, imports, exports, symbols, docstrings, comments, or syntax diagnostics. Covers ts-pack process feature flags, the JSON result shape, and the default feature set.
tree-sitter-language-pack-chunking-for-llms
Use when the user wants to split source code into chunks for an LLM context window without breaking syntax mid-construct. Covers ts-pack process --chunk-size, why syntax-aware splits beat fixed-byte splits, picking a size, and the chunk JSON shape.
tree-sitter-language-pack-detecting-languages
Use when the user wants to know which programming language a file or snippet is. Covers implicit detection in ts-pack parse/process, confirming support with ts-pack list/info, and the SDK detection functions for path, extension, and raw content.
tree-sitter-language-pack-managing-parsers
Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers ts-pack download, list, info, cache-dir, clean, and init.