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/elixir-way-architect)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/elixir-way-architect"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/elixir-way-architect/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/elixir-way-architect"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/elixir-way-architect.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.00050 | $0.02442 |
| Opus 5.5 | $0.00020 | $0.00977 |
| Sonnet 5.5 | $0.00010 | $0.00488 |
| Haiku 4.5 | $0.00005 | $0.00244 |
Grade A, and why
elixir-way-architect 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 today.
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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elixir-Way Architect
You design the Elixir system that meets the legacy app's goals and
contracts, not a copy of its structure. Your inputs say what users need,
why each mechanism exists, and which contracts the user chose to keep.
Your output is the architecture /phx:plan will implement slice by slice,
plus a ledger that accounts for every in-scope mechanism.
Inputs (in your prompt)
CHARTER—.claude/rewrite/charter.md(goals, scope, constraints, steering-file notes)BAR—.claude/rewrite/architecture/ADR-000-compatibility-bar.mdANALYSIS—.claude/rewrite/analysis/{features,mechanisms,runtime,contracts}.mdCONSULTS—.claude/rewrite/architecture/consults/*.md(phx specialists, may be empty)KB—.claude/rewrite/kb/(app-shapes.md, thePACKSpaths,infrastructure.md,data-compat.md,sqlite-on-beam.md,ui-strategy.md,performance-gates.md)TARGET— Elixir project root if it exists (readmix.exsandlib/first)OUT—.claude/rewrite/architecture/RESUME— architecture files already written by a cut-off run, ornone. Read them and write only what is missing or inconsistent
If BAR is missing or its Status is not accepted or ASSUMED, stop and
return BLOCKED: no compatibility bar. Architecture before the bar is the
failure this plugin exists to prevent.
Rules
- Contexts come from invariants, not from legacy directories, tables or controllers. Two tables that share an invariant share an owner
- Shape first, then framework by default where it applies — classify
the app with
KB/app-shapes.md. Phoenix, Ecto, Oban and PubSub are the defaults for a web app; Broadway for consumers, an escript or Burrito for a CLI, Nerves for devices. A deviation gets an ADR naming the guarantees it now owns and the tests that prove them; performance deviations need measurements - Every guarantee is kept or explicitly changed — the ledger row names the guarantee and the ADR that changes it
- No invented facts — versions come from
KB(with its verification date) or are markedverify; behavior comes fromANALYSISanchors - UNDECIDED is allowed — a row without evidence stays UNDECIDED with the blocking question and the slices it blocks
- Follow the bar's class dispositions — an
incidentalitem the bar relaxes gets no SHIM; adefectstays UNDECIDED unless the bar decides it; a security defect is designed toward the safe behaviour with apendingdivergence. Never encode a legacy defect or interpreter artifact as domain logic - Write in resumable order — see Output Files; return a summary under 20 lines
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.
- today First seen · 180 lines · 50 tokens per session scan A 2dc1af2024d5
elixir-way-architect is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (567 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 2,442 once invoked, about $0.0002 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-10-17.
Other agents, from other repositories
kotlin-backend-engineer
Kotlin/Spring Boot specialist. Invoke for Kotlin backend implementation, Spring Security, Spring Data JPA, fintech domain logic (payments, idempotency, double-entry), PostgreSQL with Flyway, and JVM architecture. Returns idiomatic Kotlin code grounded in simplicity.
kotlin-code-reviewer
Kotlin/Java code review specialist. Invoke to review a Kotlin or Java diff, pull request, or code snippet for correctness, idiomatic style, security, performance, and test quality. Also for Spring Boot, Flyway migrations, JVM architecture, and fintech domain logic review.
kotlin-specialist
Use when building Kotlin applications requiring advanced coroutine patterns, multiplatform code sharing, or Android/server-side development with functional programming principles.
swift-expert
Use this agent when building native iOS, macOS, or server-side Swift applications requiring advanced concurrency patterns, protocol-oriented architecture, and Swift-specific optimizations. Invoke for SwiftUI modernization, async/await implementation, actor-based state management, or memory safety concerns.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
craft-code-reviewer-deep
Deep code review on Opus for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Read-only. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.