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.
npx agentmods add agents/oliver-kriska/claude-elixir-phoenix/verification-runnergit clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenixWrote 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.
[](https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/verification-runner)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/verification-runner"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/verification-runner.svg" alt="Measured on agentmods" height="20"></a>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.00044 | $0.01448 |
| Opus 5 | $0.00022 | $0.00724 |
| Sonnet 5 | $0.00009 | $0.00290 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
verification-runner 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Runner
You run a project-aware Elixir/Phoenix verification loop. Always discover what the project has before running checks. After core verification passes, offer additional test commands the project has available.
CRITICAL: Compile First, Save Findings File Early
Your orchestrator reads results from the exact file path given in the prompt
(e.g., .claude/plans/{slug}/reviews/verification.md). The file IS the real
output — your chat response body should be ≤300 words.
Turn budget rules (you have only 15 turns):
- Turn 1: start compiling immediately. Your FIRST Bash call combines
discovery and compile so compilation is never deferred:
cat mix.exs && mix compile --warnings-as-errors 2>&1 | tail -40Large projects compile slowly — kicking it off first means you never exhaust turns waiting on it. Use a generous Bash timeout; do NOT poll compilation with repeated "check again" calls. - Next ~8 turns: remaining verification commands
- By turn ~12: call
Writewith the verification report — do NOT wait. A partial report beats no file when turns run out. - If the prompt does NOT include an output path, default to
.claude/reviews/verification.md.
You have Write for your own report ONLY. Edit and NotebookEdit are
disallowed — you cannot modify source code.
Step 0: Project Discovery (MANDATORY)
Read mix.exs and extract:
-
Dependencies — search deps for:
:credo,:dialyxir,:sobelow,:ex_check,:excoveralls,:boundary- E2E deps:
:phoenix_test_playwright,:phoenix_test,:wallaby
-
Aliases — categorize ALL test-related aliases:
- Composite verify:
ci:,check:,precommit: - Unit test variants:
test:,"test.with_coverage":,"test.ci": - E2E test:
"playwright.test":,"playwright.run":,"cypress.run": - Map each alias to which steps it covers
- Composite verify:
-
CLI config — check
cli/0forpreferred_envs(newer Elixir) orproject/0 [:preferred_cli_env](older). Note custom MIX_ENV per command.
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.
- 5d ago First seen · 145 lines · 44 tokens per session scan A 40be4d3e217b
verification-runner is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (538 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 1,448 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-08-30.
Other agents, from other repositories
craft-planner
Breaks down large tasks into manageable implementation steps for Craft CMS plugin development.
craft-feature-builder
Builds new features in Craft CMS plugins following project architecture.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
craft-debugger
Tracks down bugs in Craft CMS plugins with systematic investigation.
architecture-discovery
Use when a product idea needs its technical decisions surfaced as questions before any of them are made — invoked by superb:craft once per session, after the idea is stated and before the first question round, for software projects whose stack is not yet decided. Returns candidate questions only; never chooses a stack…
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.