elixir-pro

elixir-pro is a skill for Claude Code, Codex from jscraik/Agent-Skills. It costs 40 tokens per session (671 once invoked), scanned A, original, Apache-2.0.

A set of practical guidelines for writing and reviewing Elixir applications using OTP, Phoenix LiveView, supervision trees, and concurrent processes.

In plain words
What is it for?
Use it to build or debug Elixir services, review supervision structures, define process lifecycles, and improve fault tolerance.
Why use it?
It helps keep process boundaries clear, make failures recoverable, and prevent unreliable state and message handling.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build or debug Elixir services, review supervision structures, define process lifecycles, and improve fault tolerance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jscraik/agent-skills/elixir-pro
Install

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.

Any agent
npx skills add jscraik/Agent-Skills --skill elixir-pro
Clone the repo
git clone --depth 1 https://github.com/jscraik/Agent-Skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for elixir-pro

README.md
[![agentmods](https://agentmods.dev/badge/skills/jscraik/agent-skills/elixir-pro/github.svg)](https://agentmods.dev/skills/jscraik/agent-skills/elixir-pro)
Your own site
<a href="https://agentmods.dev/skills/jscraik/agent-skills/elixir-pro"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/elixir-pro/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.

agentmods 80×15 button for elixir-pro

Your own site · 80×15
<a href="https://agentmods.dev/skills/jscraik/agent-skills/elixir-pro"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/elixir-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 671 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
SkillSpector: 1 finding, up to low

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • low Excessive Agency · line 99
    Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
    Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00671
Opus 5 $0.00020 $0.00336
Sonnet 5 $0.00008 $0.00134
Haiku 4.5 $0.00004 $0.00067

Measured 6d ago against content hash e2ac15365a68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

elixir-pro 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 6d 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.

Skills/agent-ops/elixir-pro/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Table of Contents

When to use

  • Use for Elixir/OTP implementation and review work.
  • Use when fault tolerance or process boundaries are central.

Required inputs

  • App context and supervision tree scope.
  • Expected process lifecycle behavior.
  • Error and retry expectations.

Deliverables

  • Idiomatic Elixir updates.
  • Clear OTP process boundaries.
  • Explicit reliability notes when behavior changes.

OTP Structure

  • Keep supervision trees explicit and shallow.
  • Model long-lived state with GenServer only when state is required.
  • Prefer pure modules for domain logic outside process boundaries.

Reliability

  • Let supervisors restart failed workers.
  • Use pattern matching to make invalid states impossible.
  • Keep message protocols explicit and documented.

Examples

defmodule PortParser do
  def parse(value) do
    case Integer.parse(value) do
      {port, ""} when port > 0 -> {:ok, port}
      _ -> {:error, :invalid_port}
    end
  end
end

Failure mode

  • If supervision strategy is unclear, hold structural changes and confirm intent.

Gotchas

  • Process state mutations without clear ownership cause flaky behavior.

See Also

Skill When to use
[[rust-pro]] Systems-level concurrency patterns that share OTP-style supervision thinking
[[he-fix-bugs]] Triage distributed process failures with evidence-first diagnosis

Topic map: [[agent-ops]]

Philosophy

  • Optimize for clear, verifiable outcomes with the minimum necessary changes.
  • Keep guidance deterministic so repeated runs produce consistent decisions.

Procedure

  1. Confirm scope, constraints, and required inputs before edits.
  2. Apply focused changes tied directly to the requested outcome.
  3. Re-run the highest-signal validations and capture concrete evidence.

Read the full file on GitHub · 112 lines

Files

What ships with it

4 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.

Changes

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.

  1. 6d ago First seen · 112 lines · 40 tokens per session scan A e2ac15365a68

Subscribe to this mod's changes

elixir-pro is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 8d ago), licensed Apache-2.0. It adds 40 tokens to every session and 671 once invoked, about $0.0002 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.