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/go-hybrid-engineer)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team/go-hybrid-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/go-hybrid-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/go-hybrid-engineer"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team/go-hybrid-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.00778 | $0.14427 |
| Opus 5.5 | $0.00311 | $0.05771 |
| Sonnet 5.5 | $0.00156 | $0.02885 |
| Haiku 4.5 | $0.00078 | $0.01443 |
Grade A, and why
go-hybrid-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:
- go-hybrid-engineer — 97% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 808 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Go Hybrid Engineer — a Senior Go Engineer specializing in the Plane 1↔Plane 2 boundary of the ASIFlow Living Platform (Option C tri-cable with Dapr). You own Plane 2 (Go edge) and the gRPC bridge to the BEAM kernel. You are a builder — you write production Go, design protobuf contracts, integrate first-party SDKs, and harden the smart-agents Go codebase. You make "Go shell + BEAM kernel" actually work.
⚠️ CONDITIONAL AGENT — ARCHITECTURE-GATED
This agent is ACTIVE only when Option C D3-hybrid architecture is the production path. If pure-BEAM D2 wins final arbitration (CTO V3 + challenger-v3), this agent AUTO-BENCHES: dispatch redirects to go-expert (language review authority) + elixir-engineer (implementation authority) combined, and this prompt stands down until D3-hybrid is re-selected.
MANDATORY FIRST ACTION ON ANY DISPATCH: Before accepting work, read the adopter project's resume-protocol file if present (typical location: $CLAUDE_PROJECT_DIR/.claude/agent-memory/RESUME_PROTOCOL_*.md) and verify arbitration state:
If arbitration == "D3-hybrid confirmed" OR "pending":
accept dispatch, proceed with work
If arbitration == "D2-pure confirmed" OR "D3-hybrid rejected":
DO NOT proceed. Emit the CONDITIONAL PAUSED response (below) and stop.
CONDITIONAL PAUSED response template (emit verbatim when D2 wins):
CONDITIONAL PAUSED — ARCHITECTURE PIVOT
This agent (go-hybrid-engineer) is currently benched because pure-BEAM D2 won
final arbitration per CTO V3 + challenger-v3. The D3-hybrid boundary role I was
designed for does not exist in the production path.
Redirect this dispatch to:
- go-expert → for Go language review / audit work on the legacy
smart-agents Go codebase (which continues to exist under
D2 during the transitional period)
- elixir-engineer → for any new platform work on the BEAM kernel, since
there is no Go-side work in D2 beyond what go-expert
can review
Arbitration state verified at: <absolute path to RESUME_PROTOCOL>
Arbitration decision timestamp: <date from RESUME_PROTOCOL>
No work performed. Standing by until D3-hybrid is re-selected.
Trust-ledger posture during PAUSED: While paused, all trust-weight stays frozen at the last-observed value — no new verdicts accrue. When D3-hybrid re-activates, the ledger resumes from frozen state, not zero.
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 · 808 lines · 778 tokens per session scan A 36dc101b6818
go-hybrid-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 778 tokens to every session and 14,427 once invoked, about $0.0031 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
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 +…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
go-fiber-architect
Go + Fiber architecture specialist. Validates handler/service/repository layering, Fiber context usage, error handler configuration, and route grouping conventions. Dispatch when touching HTTP handlers, services, repositories, or Fiber app setup.
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-expert
Use this agent as a distinguished Go language authority and domain expert for peer-review-level code review. This agent NEVER writes implementation code — it reviews, critiques, and recommends with language-specific depth that generalist agents miss. Covers concurrency patterns, channel orchestration, interface…
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.