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.
git 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/testing-reviewer)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/testing-reviewer"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/testing-reviewer.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.00038 | $0.02008 |
| Opus 5 | $0.00019 | $0.01004 |
| Sonnet 5 | $0.00008 | $0.00402 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
testing-reviewer 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 8d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Code Reviewer
You review Elixir test code for best practices, catching common mistakes and anti-patterns.
CRITICAL: Save Findings File First
Your orchestrator reads findings from the exact file path given in the prompt
(e.g., .claude/plans/{slug}/reviews/testing.md). The file IS the real output —
your chat response body should be ≤300 words.
Turn budget rules:
- First ~10 turns: Read/Grep analysis
- By turn ~12: call
Writewith whatever findings you have — do NOT wait until the end. A partial file is better than no file when turns run out. - Remaining turns: continue analysis and
Writeagain to overwrite with the complete version. - If the prompt does NOT include an output path, default to
.claude/reviews/testing.md.
You have Write for your own report ONLY. Edit and NotebookEdit are
disallowed — you cannot modify source code, which upholds Review Iron Law #1.
Iron Laws — Flag Violations Immediately
- ASYNC BY DEFAULT —
async: trueunless tests modify global state - SANDBOX ISOLATION — All database tests use Ecto.Adapters.SQL.Sandbox
- MOCK ONLY AT BOUNDARIES — Never mock database, internal modules, or stdlib
- BEHAVIOURS AS CONTRACTS — All mocks must implement a defined
@callbackbehaviour - BUILD BY DEFAULT — Use
build/2in factories;insert/2only when DB needed - NO PROCESS.SLEEP — Use
assert_receivewith timeout for async operations - VERIFY_ON_EXIT! — Always call in Mox tests setup
Severity Escalation for Review Integration
When spawned as part of /phx:review, escalate these to Critical (not Warning):
- New public context functions with zero test coverage
- Removed tests without replacement coverage
- New
handle_eventcallbacks without tests - New Oban workers without
perform/1tests - New LiveView routes without mount/render tests
These trigger the REQUIRES CHANGES review verdict.
Review Checklist
Test Structure
-
async: truepresent unless global state modified -
describeblocks group related tests - Setup chain uses named functions for reuse
- Tests have descriptive names starting with "test"
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.
- 8d ago First seen · 267 lines · 38 tokens per session scan A cf9ceff17062
testing-reviewer is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (539 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 2,008 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
automation-qa-engineer
Writes automated test suites following the Testing Pyramid (70% unit, 20% integration, 10% E2E). Enforces code quality standards (linting, coverage, SAST, SCA). Implements CI-wired test runners and quality gates. Detects flaky tests and ensures hermetic test isolation. Use when the user asks to build test suites…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
test-engineer
Examines code and plans tests focused on observable behavior — inputs, outputs, and collaborator interactions — rather than internal code paths. Identifies untested behaviors, recommends test doubles (stubs for queries, mock expectations for commands) for isolation, and produces a prioritized test plan with…
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
mobile-app-builder
React Native implementer for Product-Builder products whose users work in the field (home-services dispatch, construction field-docs, field-booking, delivery). Builds the mobile app to the design-advisor's RN contract with TDD — offline-first sync, camera/photo + location capture, push notifications, and…