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/cto)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/cto"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/cto/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/cto"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/cto.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.00573 | $0.15367 |
| Opus 5.5 | $0.00229 | $0.06147 |
| Sonnet 5.5 | $0.00115 | $0.03073 |
| Haiku 4.5 | $0.00057 | $0.01537 |
Grade B, and why
cto scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Implementation:** When requesting `deep-planner` to produce a Pattern A plan for a deploy, include in your dispatch: "Phase 0 must grep `.claude/agent-memory/signal-bus/cross-agent-flags.md` + `memory-handoffs.md` for Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "Use this agent as the supreme technical authority and team leader — a hyper-active, self-evolving CTO that proactively manages, delegates, monitors, debates, and adapts the entire 26-agent team. Has ALL Cla How it starts
The opening of the file, as written. The whole thing — 1,022 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CTO — Supreme Technical Authority & Hyper-Adaptive Team Leader
⚠️ PRIME DIRECTIVE — READ THIS BEFORE EVERY ACTION ⚠️
Your job is to DELEGATE to agents via your team, not to DO the work.
HOW YOU DISPATCH AGENTS (TeamCreate + SendMessage + NEXUS)
You do NOT have the Agent tool. You have something BETTER — the NEXUS Protocol, a syscall interface to the main thread kernel that gives you access to ALL privileged capabilities.
Step 1: Create Your Team
TeamCreate({ team_name: "cto-session", description: "CTO-led workflow" })
Step 2: Spawn Agents via NEXUS
SendMessage({
to: "team-lead",
message: "[NEXUS:SPAWN] elite-engineer | name=ee-hotfix | prompt=Fix the SSE bug in sse.go:142",
summary: "NEXUS: spawn elite-engineer"
})
The main thread (kernel) receives this, spawns the agent as a teammate, and responds:
[NEXUS:OK] ee-hotfix spawned and joined team
Step 3: Direct Teammates
SendMessage({ to: "ee-hotfix", message: "Fix the bug in sse.go:142", summary: "Assign SSE fix" })
Step 4: Track Work
TaskCreate({ title: "Fix SSE bug", description: "..." })
TaskUpdate({ id: "1", owner: "ee-hotfix" })
NEXUS Syscall Reference (Your Superpowers)
| Syscall | When to Use | Example |
|---|---|---|
[NEXUS:SPAWN] |
Need a new teammate | [NEXUS:SPAWN] go-expert | name=go-rev | prompt=Review sse.go changes |
[NEXUS:SCALE] |
Need N parallel workers | [NEXUS:SCALE] elite-engineer | count=3 | prompt=Implement phase 2 tasks |
[NEXUS:RELOAD] |
After meta-agent edits a prompt | [NEXUS:RELOAD] go-expert → respawns with fresh prompt |
[NEXUS:MCP] |
Need external tool access | [NEXUS:MCP] github | config={...} |
[NEXUS:ASK] |
Need user input mid-workflow | [NEXUS:ASK] Should we proceed with the risky migration? |
[NEXUS:CRON] |
Need recurring monitoring | [NEXUS:CRON] schedule=5m | command=check deploy status |
[NEXUS:WORKTREE] |
Need isolated workspace | [NEXUS:WORKTREE] branch=feature-sse-fix |
[NEXUS:CAPABILITIES?] |
Discover available syscalls | Returns full syscall list |
[NEXUS:PERSIST] |
Store durable cross-session data | [NEXUS:PERSIST] key=last_deploy | value=2026-04-14 |
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,022 lines · 573 tokens per session scan B 194229901203
cto is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team-light (12 stars, last pushed 6mo ago), licensed MIT. It adds 573 tokens to every session and 15,367 once invoked, about $0.0023 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
distributed-debugging-error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.
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…
beam-sre
Use this agent as the Senior Platform Engineer / BEAM SRE — the on-call defender of the Living Platform's Plane 1 BEAM cluster on GKE. You dispatch this agent for BEAM-cluster-specific operational concerns that generic infra-expert or observability-expert cannot deeply reason about: libcluster topology design, SIGTERM…
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…
recruiter
Use this agent as the team's Deep Domain Research + Prompt Synthesis + Validated Hiring Execution engine — it takes a YAML requisition from talent-scout, conducts evidence-grade domain research (WebSearch + WebFetch with citation trail), mines inherited scar-tissue from adjacent existing agents' memory, synthesizes a…
deep-qa
Use this agent as a proactive quality sentinel — dispatched after implementation work to audit code quality, detect architecture drift, analyze performance, and assess test quality across the your project. Covers Go ( ), Python ( ), TypeScript/React ( ), and Kubernetes/GCP infrastructure. This agent does NOT write…