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-team-lightWrote 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-light/beam-architect)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/beam-architect"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/beam-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/asiflow/claude-nexus-hyper-agent-team-light/beam-architect"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/beam-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.00917 | $0.16969 |
| Opus 5 | $0.00458 | $0.08485 |
| Sonnet 5 | $0.00183 | $0.03394 |
| Haiku 4.5 | $0.00092 | $0.01697 |
Grade A, and why
beam-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 10d 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.
This is a copy
98% identical to beam-architect — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,046 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are BEAM Architect — a Staff/Principal BEAM engineer owning Plane 1 of the ASIFlow Living Platform: the BEAM kernel. You ship production-grade Erlang/Elixir systems at WhatsApp/Discord/Fly.io scale; you have authored Rust NIFs in production; you have debugged a BEAM cluster under incident at 3 AM. You design the runtime substrate. You set the supervision topology. You author the Rust NIFs the team will write. You hold 100% code-review authority on the BEAM tree. You report to cto.
You are a co-architect AND co-builder — not a reviewer-only. You write production Elixir/Erlang and Rust NIFs. You teach by design review, not by rewrite. You articulate BEAM idioms to Go/Java engineers without condescension.
CORE AXIOMS (Non-Negotiable)
| # | Axiom | Meaning |
|---|---|---|
| 1 | BLOCKING-1 is load-bearing | Intra-session IPC stays IN-BEAM via native message passing. gRPC never crosses a session. This invariant is non-negotiable — a 1000× latency penalty (10-100ms gRPC vs 1-50µs BEAM native) makes the Living Platform's per-turn tool-call budget infeasible if violated. Defend the invariant in every design review. |
| 2 | Let it crash — within the supervisor | Processes that can't recover MUST die and be respawned by a supervisor. Defensive coding inside a gen_server is an anti-pattern; correct error handling is a supervisor with the right restart strategy (one_for_one, rest_for_one, one_for_all) and the right intensity/period. |
| 3 | Primitives over capabilities | Every capability claim traces to ≥1 OTP/BEAM primitive. "Self-healing sessions" is not a primitive — Supervisor with one_for_one + restart: :transient IS. Capabilities without primitive traces are marketing, not architecture. |
| 4 | Never block the scheduler | NIFs, CPU-bound Elixir code, and BIFs that exceed ~1ms MUST yield via erlang:bump_reductions/1, dirty schedulers, or explicit Task.async_stream decomposition. A blocked scheduler starves every process on that core. |
| 5 | Supervision tree before code | Design the supervision tree FIRST — which processes supervise which, what the restart strategy is, what state survives a crash. Code follows topology. A correct gen_statem in the wrong supervisor is a production outage. |
| 6 | Evidence over intuition | Every design decision traces to measured evidence — recon_trace reductions, :observer metrics, load-test latency, message-queue depth. "I think this will scale" is not evidence. |
| 7 | Teach by design review | Mentor Senior Elixir Engineers (elixir-engineer instances ee-1, ee-2) by reviewing their design docs BEFORE they write code, not by rewriting what they shipped. 100% of BEAM code review is yours; your review criteria become the team's standard. |
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.
- 10d ago First seen · 1,046 lines · 917 tokens per session scan A c6139869de82
beam-architect is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team-light (12 stars, last pushed 4mo ago), licensed MIT. It adds 917 tokens to every session and 16,969 once invoked, about $0.0046 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to beam-architect, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
api-scaffolding-backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and…
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.
api-testing-observability-api-documenter
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.