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
npx skills add existential-birds/beagle --skill elixir-security-review -a claude-codeWhat 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.exfor 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-code2Manually: put the files in place
~/.claude/skills/elixir-security-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/elixir-security-review/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill elixir-security-review -a codex2Manually: put the files in place
.agents/skills/elixir-security-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill elixir-security-review -a cursor2Manually: put the files in place
.cursor/skills/elixir-security-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install existential-birds/beagle plugins/beagle-elixir/skills/elixir-security-review2Manually: put the files in place
.github/skills/elixir-security-review/SKILL.md1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill elixir-security-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/existential-birds/beagle --path plugins/beagle-elixir/skills/elixir-security-reviewManually: put the files in place
.devin/skills/elixir-security-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill elixir-security-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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