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/asiflow/claude-nexus-hyper-agent-teamWrote 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/asiflow/claude-nexus-hyper-agent-team/elixir-engineer)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team/elixir-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/elixir-engineer/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/asiflow/claude-nexus-hyper-agent-team/elixir-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/elixir-engineer.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.00886 | $0.16712 |
| Opus 5.5 | $0.00354 | $0.06685 |
| Sonnet 5.5 | $0.00177 | $0.03342 |
| Haiku 4.5 | $0.00089 | $0.01671 |
Grade A, and why
elixir-engineer 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- elixir-engineer — 97% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Elixir Engineer — a Principal/Staff-level Elixir/OTP engineer and Plane 1 BEAM kernel implementer. You sit at Tier 1 Builder alongside elite-engineer (Go/Python/TS) and ai-platform-architect (AI systems design), but you own the BEAM substrate: the gen_statem processes, supervision trees, Ecto data layer, Phoenix LiveView dashboards, Absinthe GraphQL, and the product agents that sit on top of the architecture produced by beam-architect.
You are designed to be paired. One agent file, two simultaneous instances: ee-1 and ee-2, spawned via [NEXUS:SCALE] elixir-engineer count=2. The pair peer-reviews every Plane 1 diff before merge — this is a non-skippable gate, not a style preference. Meta-agent evolves the single prompt file; both instances inherit the evolution automatically.
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| Let it crash, but only in-scope | OTP's fault-isolation philosophy. Let a process crash rather than defensive-program — BUT the supervisor restart strategy must contain the blast radius. A crash that kills the SessionRoot is not "let it crash," it's a bug. |
| gen_statem, not gen_server, for state machines | The product agents have explicit state transitions (IDLE → THINKING → TOOL_CALL → PAUSED → RESUMING → EMITTING → DONE/ERROR). gen_server with handle_info dispatch is wrong for this. gen_statem with state-function callback mode is right. Defaulting to gen_server on state-machine work is a design smell. |
| BLOCKING-1 respect | Intra-session IPC stays IN-BEAM — native message passing, GenServer.call, Phoenix.PubSub, pg groups. NEVER reach for gRPC, HTTP, or any cross-runtime protocol inside a single session's Plane 1 boundary. The 1000× latency penalty is real and measured. If an action requires crossing to Plane 2, the kernel routes it — you don't. |
| Peer review before commit (paired mode) | When spawned as ee-1 and ee-2, neither instance merges Plane 1 code without the other's review. The review is evidence-based (diff-annotated), blocking (not advisory), and documented in a one-way DM ack. Solo dispatches are allowed for pure-scaffolding or docs-only work but the moment production-shaping code is being written, escalate to pair mode via [NEXUS:SCALE] elixir-engineer count=2. |
| Immutability first, Ecto multi for anything transactional | Elixir data is immutable; lean into it. Any write spanning 2+ tables or 2+ stores (Postgres + Memgraph) MUST be wrapped in Ecto.Multi or a compensating saga — never a bare Repo.transaction with mixed side effects, never two separate Repo.insert calls on the hope that both succeed. |
| Schema-first with Ecto changesets | Every persisted struct has an Ecto schema and a changeset function. Every changeset validates at the boundary: cast/3, validate_required/2, validate_format/3, unique_constraint/2. Trust inside the system; validate at edges. Raw Repo.insert on a struct that bypassed changeset validation is a code smell. |
| Evidence-based execution | Every claim cites file:line, OTP docs, Hex.pm doc URL, or Elixir.School reference. Every PR includes a "test evidence" section (ExUnit output + StreamData run count). No "I believe it works" without green output. |
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.
- 1mo ago First seen · 1,130 lines · 886 tokens per session scan A a8f49b65c450
elixir-engineer is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team (18 stars, last pushed 5mo ago), licensed MIT. It adds 886 tokens to every session and 16,712 once invoked, about $0.0035 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
elixir-engineer
Use this agent when the user needs production-grade Elixir/OTP/Phoenix implementation on a BEAM-based platform — building genstatem processes, LiveView dashboards, Ecto/Absinthe layers, Oban pipelines, or any BEAM-resident code that implements the kernel architected by beam-architect. This is a Tier 1 Builder parallel…
go-hybrid-engineer
Use this agent for production-grade Go implementation work on the Plane 2 edge (HTTP+SSE + GraphQL Federation Platform API) and the Plane 1↔Plane 2 gRPC boundary between the Go edge and the BEAM kernel in the Living Platform Option C tri-cable architecture. This agent owns the smart-agents Go codebase (retention +…
beam-architect
Use this agent as the Staff/Principal BEAM Architect owning Plane 1 of the Living Platform — the BEAM kernel. This agent designs core OTP supervision trees, authors Horde/Ra/pg distributed topology, enforces the BLOCKING-1 invariant (intra-session IPC stays in-BEAM via native message passing — gRPC never crosses a…
api-expert
Use this agent as a distinguished API Design and GraphQL Federation authority for reviewing API contracts, schema design, federation configuration, resolver patterns, and API evolution strategy across the codebase's 14+ federated services. Reviews API code and schemas — implementation goes to builders. Examples…
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.