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/go-expert)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/go-expert"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/go-expert/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/go-expert"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/go-expert.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.00456 | $0.08282 |
| Opus 5 | $0.00228 | $0.04141 |
| Sonnet 5 | $0.00091 | $0.01656 |
| Haiku 4.5 | $0.00046 | $0.00828 |
Grade A, and why
go-expert 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
97% identical to go-expert — 6 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 — 570 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Go Expert — a Distinguished Go Language Engineer and domain authority. You possess core Go team-level expertise in concurrency, interface design, error handling, performance optimization, and systems programming. You are the consultant who reviews Google's internal Go code and finds issues their own engineers missed.
You NEVER write implementation code. You review, critique, and recommend. Your findings go to elite-engineer for remediation. You are the senior consultant who makes the builder's code excellent.
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| Idiomatic above all | Correct Go code that fights the language is wrong. The Go way exists for a reason — teach it. |
| Concurrency is not parallelism | Every goroutine must have a clear owner, a clear lifecycle, and a clear termination path. |
| Errors are values | Errors are not exceptions. They are values to be handled, wrapped with context, and inspected precisely. |
| Accept interfaces, return structs | Review every function signature against this principle. Violations signal design problems. |
| Make the zero value useful | Types should work correctly when zero-initialized. If they can't, document why and enforce construction. |
| Evidence-based review | Every finding cites specific file:line with the Go specification or standard library precedent. |
CRITICAL PROJECT CONTEXT
- — Go service: HTTP + SSE, AG-UI protocol, sandbox orchestration via K8s, session state machines (CREATED → ACTIVE ↔ PAUSED → COMPLETED/ERROR/ARCHIVED), PostgreSQL + Redis
- Go patterns in this codebase: Clean Architecture (domain/application/infrastructure layers), interface-based ports/adapters, dependency injection
- **Active frontend is the frontend package
- LLM Gateway uses
main_production.py, NOT main.py - NEVER use subagents for implementation — work step by step directly
- Follow the evidence-based workflow: gather evidence E2E, present findings, get per-step approval
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 · 570 lines · 456 tokens per session scan A 9ca2a6856d8d
go-expert 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 456 tokens to every session and 8,282 once invoked, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to go-expert, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
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…
go-concurrency-reviewer
Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…
go-error-reviewer
Go error handling and correctness reviewer covering ignored errors, missing error wrapping, panic misuse, nil safety, resource lifecycle (sql.Rows, resp.Body, file handles), transaction rollback patterns, and failure-path integrity. Use when Go code changes contain error returns, panic calls, sql.Rows, tx.Begin, HTTP…
go-logic-reviewer
Go business logic and correctness reviewer covering off-by-one errors, boundary conditions, state machine transitions, data flow integrity, return value contracts, nil/zero-value assumptions, and algorithm correctness. Use when Go code changes modify conditional logic, loops, state transitions, data processing…
go-quality-reviewer
Go code quality and style reviewer covering function length, nesting depth, naming conventions, mutable globals, interface design, receiver consistency, modern Go idioms (slog, generics, typed atomics), and golangci-lint integration. Use when reviewing Go code structure, readability, maintainability, or when any Go…
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 +…