A verification loop for Elixir and Phoenix projects that discovers the project's configured checks before running them. It can format, compile, and run tests in the order the project expects.

Use it after implementing or fixing code, before a pull request, or whenever you need evidence that an Elixir or Phoenix project still passes its checks.

It reduces the risk of using the wrong command or claiming a change works without actual test output. It also separates automatic unit checks from tests that need confirmation.

verify — Skill for Claude Code by oliver-kriska/claude-elixir-phoenix

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 oliver-kriska/claude-elixir-phoenix --skill verify

Clone the repo

git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix

Made for: Claude Code.

Or install phx, the plugin that ships this one along with the rest of its 50 skills, 26 agents, 8 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/verify/github.svg)](https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/verify)

Your own site

<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/verify"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/verify/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/verify"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,372 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

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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.01372
Opus 5.5	$0.00013	$0.00549
Sonnet 5.5	$0.00007	$0.00274
Haiku 4.5	$0.00003	$0.00137

Measured 23d ago against content hash b3969de5ca9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify 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 23d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

phx-verify — 98% identical, 12 lines differ
elixir-phoenix-verify — 91% identical, 20 lines differ

plugins/elixir-phoenix/skills/verify/SKILL.md · 123 lines

How it starts

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

Verification Loop

Project-aware verification for Elixir/Phoenix. Reads mix.exs and .check.exs to discover tools, test commands, and custom aliases before running anything.

Iron Laws

Discover before running — Read mix.exs first; never run mix credo if credo isn't a dependency
Prefer ex_check — If :ex_check + .check.exs exists, mix check replaces individual steps
Prefer project aliases — If mix ci or composite alias exists, use it over individual steps
Run in order — Later steps assume earlier ones pass
Ask before E2E tests — Unit tests run automatically; E2E/integration tests need user confirmation
NEVER report success without showing actual command output — "should work" is not verification

Step 0: Project Discovery (ALWAYS FIRST)

Read mix.exs — extract deps/0, aliases/0, and cli/0 (for preferred_envs). Also check for .check.exs. See ${CLAUDE_SKILL_DIR}/references/project-discovery.md for full patterns.

Discover tools (deps): :credo, :dialyxir, :sobelow, :ex_check, :excoveralls, :boundary

Discover test commands (aliases + deps):

Unit: mix test (always), or custom alias like mix test.with_coverage
E2E: mix playwright.test, mix cypress.run, or similar (check preferred_envs for MIX_ENV)
Fast E2E: mix playwright.run (skips setup — for re-runs)

Discover composite runner: If .check.exs exists, read it — mix check may handle compile, format, credo, test, dialyzer, sobelow, and more.

Report discovery:

Project tools: compile ✓ | format ✓ | credo ✓ | dialyzer ✓ | sobelow ✓ | ex_check ✓
Test commands: mix test (unit) | mix playwright.test (E2E, MIX_ENV=int_test)
Composite runner: mix check (.check.exs covers: compiler, formatter, credo, dialyzer, sobelow, tests)
Strategy: Running `mix check` then asking about E2E

Verification Sequence

Before using any discovered alias or composite command, confirm it runs:

Check the dependency is in mix.lock (not just mix.exs) — deps may not be fetched
Run the command — if it fails with "command not found" or dependency error, fall back to individual steps
Log the fallback: "mix check failed (ex_check not installed?), falling back to individual steps"

Read the full file on GitHub · 123 lines

Files

What ships with it

1 file 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.

references/project-discovery.md 8.4 KB

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.

23d ago Changed b3969de5ca9a
1mo ago First seen · 123 lines · 33 tokens per session scan A aab624cb6da7

Subscribe to this mod's changes

verify is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (569 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,372 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Debugging Testing automation claude claude-code-plugin claude-code-skills claude-skills

craft-pest

Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…

michtio/craftcms-claude-skills · 175 tokens

refactor-safely

Restructure existing code safely without changing externally observable behavior. Composes context, design, architecture, code quality, and testing guardrails into a characterization-first refactoring workflow. Use when the user says 'refactor this', 'clean this up', 'untangle this module', 'move this to the right…

techygarg/lattice · 82 tokens

fix-bug

Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.

QBall-Inc/the-bulwark · 46 tokens

feature-dev

Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an…

thoughtbot/rails-consultant · 83 tokens

test-driven-development

Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.

thoughtbot/rails-consultant · 68 tokens

triage-issue

Invoked helper skill for deep bug diagnosis, usually delegated from /qa when a reported issue needs root-cause analysis and a TDD fix plan before implementation. Use when the cause is unclear, the bug is a regression, or the user explicitly wants diagnosis. Not for lightweight QA intake (use /qa) or already-clear…

chrislacey89/skills · 77 tokens