Help us improve
Share bugs, ideas, or general feedback.
From beagle-elixir
Reviews Elixir code for security vulnerabilities like code injection, atom exhaustion, secrets in config, ETS exposure, and process dictionary risks. Use for code handling user input, external data, or sensitive config.
npx claudepluginhub existential-birds/beagle --plugin beagle-elixirHow this skill is triggered — by the user, by Claude, or both
Slash command
/beagle-elixir:elixir-security-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Issue Type | Reference |
Reviews Elixir .ex/.exs code for idiomatic style, pattern matching, OTP (GenServer/Supervisors), documentation (@doc/@spec), and security issues.
Enforces Elixir/Phoenix security rules for auth, tokens, redirects, user input: prevents atom exhaustion, SQL injection via Ecto fragments, open redirects. Invoke before security-sensitive code.
Reviews Elixir/Phoenix code using parallel specialist agents for tests, security, Ecto, LiveView, Oban. Identifies bugs and anti-patterns post-implementation before committing.
Share bugs, ideas, or general feedback.
| Issue Type | Reference |
|---|---|
| Code.eval_string, binary_to_term | references/code-injection.md |
| String.to_atom dangers | references/atom-exhaustion.md |
| Config, environment variables | references/secrets.md |
| ETS visibility, process dictionary | references/process-exposure.md |
Code.eval_string/1 on user input:erlang.binary_to_term/1 without :safe on untrusted dataString.to_atom/1 on external input| 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 |
Use the issue format: [FILE:LINE] ISSUE_TITLE for each finding.
Load and follow review-verification-protocol before reporting any issue.