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 | $0.00287 | $0.07684 |
| Sonnet 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 9d 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.
- 9d 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 4mo ago), licensed MIT. It adds 573 tokens to every session and 15,367 once invoked, about $0.0029 per session on Opus 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
c4-code
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. Use when documenting code at the lowest C4 level for individual directories and code modules.
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
c4-component
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
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…
c4-context
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating…
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.