Skip to main content
skill CX Codex

elixir-security-review — Claude Code skill: how to install

elixir-security-review audits Elixir code for security issues like code injection, atom table exhaustion, and exposed secrets before merging.

Apache-2.0 110 installs ★ 89 updated 2026-09-15

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add existential-birds/beagle --skill elixir-security-review -a claude-code
Open on GitHub

What elixir-security-review does

This skill inspects Elixir projects for critical vulnerabilities. It flags dangerous constructs including Code.eval_string/1 on external input, :erlang.binary_to_term/1 missing the :safe option, dynamic String.to_atom/1 calls, and secrets hardcoded in source files. It also checks ETS table visibility, process dictionary usage, and configuration handling.

Findings must pass strict pre-reporting gates. The agent must verify exact [FILE:LINE] locations, inspect the enclosing scope, and pinpoint the external data source, such as conn.params or decoded payloads. Compile-time constants and dev/test usages are recognized as valid patterns and skipped.

What it helps with

  • catch String.to_atom calls on unvalidated external inputs
  • flag unsafe :erlang.binary_to_term deserialization
  • detect secrets committed to configuration files
  • inspect ETS table access permissions for sensitive data

Example prompts for the agent

  • Review lib/my_app_web/controllers/auth_controller.ex for security issues
  • Run an Elixir security audit on the user input parsing logic

How to install elixir-security-review

1Skills CLI (Vercel)

npx skills add existential-birds/beagle --skill elixir-security-review -a claude-code

2Manually: put the files in place

~/.claude/skills/elixir-security-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/elixir-security-review/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about elixir-security-review

How do I install elixir-security-review in Claude Code?

Run npx skills add existential-birds/beagle --skill elixir-security-review -a claude-code.

What does elixir-security-review check?

It audits Elixir projects for atom exhaustion, code evaluation on untrusted data, exposed secrets in configs, and open ETS tables.

When does elixir-security-review ignore String.to_atom?

The skill skips String.to_atom when it operates on compile-time constants or internal values that do not originate from external input.

Source text

SKILL.md · Apache-2.0
---
name: elixir-security-review
description: Reviews Elixir code for security vulnerabilities including code injection, atom exhaustion, and secret handling. Use when reviewing code handling user input, external data, or sensitive configuration.
---

# Elixir Security Review

## Quick Reference

| Issue Type | Reference |
|------------|-----------|
| Code.eval_string, binary_to_term | [references/code-injection.md](references/code-injection.md) |
| String.to_atom dangers | [references/atom-exhaustion.md](references/atom-exhaustion.md) |
| Config, environment variables | [references/secrets.md](references/secrets.md) |
| ETS visibility, process dictionary | [references/process-exposure.md](references/process-exposure.md) |

## Review Checklist

### Critical (Block Merge)
- [ ] No `Code.eval_string/1` on user input
- [ ] No `:erlang.binary_to_term/1` without `:safe` on untrusted data
- [ ] No `String.to_atom/1` on external input
- [ ] No hardcoded secrets in source code

### Major
- [ ] ETS tables use appropriate access controls
- [ ] No sensitive data in process dictionary
- [ ] No dynamic module creation from user input
- [ ] Path traversal prevented in file operations

### Configuration
- [ ] Secrets loaded from environment
- [ ] No secrets in config/*.exs committed to git
- [ ] Runtime config used for deployment secrets

## Valid Patterns (Do NOT Flag)

- **String.to_atom on compile-time constants** - Atoms created at compile time are safe
- **Code.eval_string in dev/test** - May be needed for tooling
- **ETS :public tables** - Valid when intentionally shared
- **binary_to_term with :safe** - Explicitly safe option used

## Context-Sensitive Rules

| Issue | Flag ONLY IF |
|-------|--------------|
| String.to_atom | Input comes from external source (user, API, file) |
| binary_to_term | Data comes from untrusted source |
| ETS :public | Contains sensitive data |

## Hard gates (before reporting)

Complete **in order** for each finding you intend to report. Do not advance until the pass condition is satisfied.

1. **Location artifact** — The finding includes `[FILE:LINE]` (or a line range) that you copied from the current file contents; the path resolves in this repo.
2. **Scope read** — You read the full surrounding function or module section that contains the flagged code, not only a diff hunk or summary.
3. **External-data claim** (only if the finding depends on “user/untrusted input”) — You can name one concrete ingress (for example `conn.params`, `Jason.decode!/1` result, uploaded file path, message from another node) **or** you drop the finding because the value is compile-time, test-only, or internal per Context-Sensitive Rules.
4. **Protocol** — Pre-report steps in [review-verification-protocol](../review-verification-protocol/SKILL.md) are satisfied for this item (no finding if they are not).

## Before Submitting Findings

Use the issue format: `[FILE:LINE] ISSUE_TITLE` for each finding.

Hard gate 4 requires [review-verification-protocol](../review-verification-protocol/SKILL.md); use it as the full pre-report checklist and issue-type verification (it extends beyond this skill’s summary).

© existential-birds · Apache-2.0 · existential-birds/beagle

Similar skills

All skills for Security →

From the same set68

The whole set →
pydantic-ai-model-integration pydantic-ai-model-integration guides LLM provider configuration, fallback model chains, streaming, and token limits in PydanticAI. CX Codex +1 120installs review-ai-writing review-ai-writing scans documentation, docstrings, commit messages, and pull request descriptions for machine-generated writing patterns. Useful for keeping project artifacts clear and natural. CX Codex +1 119installs wish-ssh-code-review wish-ssh-code-review inspects Go SSH server code using charmbracelet/wish for middleware order, session handling, host keys, and graceful shutdown patterns. CX Codex +1 119installs urlsession-code-review urlsession-code-review reviews the networking layer of iOS and macOS apps: status codes, caching, timeouts, background sessions. Findings come with file:line. CX Codex +1 116installs elixir-performance-review elixir-performance-review is a Claude Code skill that checks Elixir code for GenServer, memory and concurrency bottlenecks when a service slows under load, with findings backed by measurement. CX Codex +1 107installs elixir-writing-docs elixir-writing-docs guides writing Elixir documentation using @moduledoc, @doc, @typedoc, doctests, and ExDoc metadata in .ex source files. CX Codex +1 106installs rust-code-review The rust-code-review Claude Code skill reviews Rust code in .rs files. It checks ownership, borrowing, error handling, traits, and unsafe code. CX Codex +1 104installs vercel-ai-sdk Vercel AI SDK patterns for building streaming chat interfaces, handling tool invocations, and rendering complex messages. CX Codex +1 101installs

Project sponsors

Companies that keep this analytics open