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 AmariahAK/atlarix-skills --skill elixirgit clone --depth 1 https://github.com/AmariahAK/atlarix-skillsWrote 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/amariahak/atlarix-skills/elixir)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/elixir"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/elixir.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.1 | $0.00003 | $0.00327 |
| Opus 5 | $0.00002 | $0.00163 |
| Sonnet 5 | $0.00001 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
Elixir Patterns 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.
What it actually says
Elixir Patterns
When to use this skill
Use this skill when working on Elixir/Phoenix projects and you want maintainable OTP-friendly structure, clear boundaries, and robust error handling.
Core patterns
Mix project hygiene
mix.exsis the source of truth- keep deps minimal and explicit
- avoid runtime config surprises (document env vars)
OTP mindset
Prefer:
- supervision trees
- isolated processes for state
- message passing over shared mutable state
Function clarity
- small functions
- pattern matching for branching
- use guard clauses for fast validation
Testing
- ExUnit for unit tests
- keep tests deterministic
Atlarix tool notes
- Explore: inspect
mix.exsandlib/modules; locate supervision tree. - Build: run
mix test. - Debug: inspect crash logs; confirm supervision restarts aren’t hiding repeated failures.
- Review: check boundaries and that errors include enough context.
Common mistakes to avoid
- Putting too much state in a single process
- Silent failures under supervisors
- Overusing macros instead of plain functions
Mini-checklist
- Supervision is intentional
- Boundaries are clear
- Tests cover critical behavior
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 · 53 lines · 3 tokens per session scan A bf184deaca58
Elixir Patterns is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 3 tokens to every session and 327 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
elixir-phoenix-testing
Apply Elixir testing patterns for ExUnit, Mox, factories, and LiveView.
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.
typescript
TypeScript strict mode with eslint and jest.
elixir
Use when writing or refactoring Elixir/OTP on the BEAM — GenServers, supervision trees and restart strategies, pattern matching, mix projects and releases — or when processes misbehave (restart loops, mailbox growth, call timeouts). NOT a Phoenix web app, LiveView, Ecto or channels (that is phoenix).
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.
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.