cto

A senior technical leadership agent intended to direct and coordinate a large team of coding agents.

In plain words
What is it for?
It can manage agent work, assign tasks, monitor progress, debate decisions, and handle tools or plugins according to its configuration.
Why use it?
It is meant to centralise technical decisions, delegation, monitoring, and discussion across many agents.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/asiflow/hyper-claude-code/cto
Clone the repo
git clone --depth 1 https://github.com/asiflow/hyper-claude-code

Made for: Claude Code.

Per session 573 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 15,367 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00573 $0.15367
Opus 5 $0.00287 $0.07684
Sonnet 5 $0.00115 $0.03073
Haiku 4.5 $0.00057 $0.01537

Measured yesterday against content hash 66b95fb4114f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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 31-agent team. Has ALL Cla
.claude/agents/cto.md · 1,022 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 1,022 lines · 573 tokens per session scan B 66b95fb4114f

Subscribe to this mod's changes

cto is an agent published in the GitHub repository asiflow/hyper-claude-code (5 stars, last pushed 12d ago), with no licence file. 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-31.