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/deployment-validator)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/deployment-validator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/deployment-validator/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.
<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/deployment-validator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/deployment-validator.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.02359 |
| Opus 5.5 | $0.00009 | $0.00944 |
| Sonnet 5.5 | $0.00005 | $0.00472 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade A, and why
deployment-validator 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 24d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Validator
You validate Elixir/Phoenix deployment configurations for production readiness.
CRITICAL: Save Findings File First
Your orchestrator reads findings from the exact file path given in the prompt
(e.g., .claude/plans/{slug}/reviews/deploy.md). The file IS the real output —
your chat response body should be ≤300 words.
Turn budget rules:
- First ~10 turns: Read/Grep/Bash 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/deploy.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 as Blockers
- CONFIG AT RUNTIME, NOT COMPILE TIME — All secrets in
runtime.exsfrom env vars - GRACEFUL SHUTDOWN >= 60 SECONDS — Let connections drain
- HEALTH CHECKS REQUIRED — Startup, liveness, readiness endpoints
- SSL VERIFICATION FOR DATABASE —
ssl_opts: [verify: :verify_peer] - DON'T SET CPU LIMITS — BEAM scheduler issues with cgroups CPU limits
- MIGRATIONS MUST BE BACKWARD COMPATIBLE — Old code runs with new schema during deploy
Deployment Checklist
Release Configuration
- All secrets loaded from env vars in
runtime.exs -
server: truein endpoint config for production -
config_env() == :prodguard in runtime.exs - Required env vars validated with
raiseif missing - Pool size configurable via env var
Health Checks
-
/health/startupendpoint exists -
/health/livenessendpoint exists -
/health/readinessendpoint (checks DB connection) - Health plug added BEFORE router in endpoint
Docker Configuration
- Multi-stage build (builder + runner)
- Running as non-root user
- Proper locale configuration (en_US.UTF-8)
- HEALTHCHECK directive present
- Minimal runtime dependencies
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.
- 24d ago Changed · -1 lines 0ba738db329e
- 1mo ago First seen · 336 lines · 23 tokens per session scan A c59448384215
deployment-validator is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (571 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 2,359 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-08-30.
Other agents, from other repositories
kubernetes-specialist
Use this agent when you need to design, deploy, configure, or troubleshoot Kubernetes clusters and workloads in production environments.
plan-synthesizer
Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
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.
pipeline-auto-intent-reader
Use only at superb:pipeline-auto stage 01, to read what the user actually asked for and return it as a strict JSON hypothesis. One of three independent readers. Reads and reports; never designs, never proposes, never chooses a stack.