cto

cto is a command for Claude Code from alirezarezvani/claude-cto-team. It costs 7 tokens per session (353 once invoked), scanned A, original, MIT.

A command that gives software-project advice at the level of a chief technology officer (CTO), a person responsible for major technical and architecture decisions. It examines a request and directs it to a suitable specialist.

In plain words
What is it for?
Use it to plan system designs, choose technologies, review technical work, debug problems, and coordinate complex requests across several specialists.
Why use it?
It helps turn vague requests into specific questions and separates planning, building, reviewing, debugging, and documentation work. This can make the needed decision and next steps clearer.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the cto-team plugin — 12 skills, 4 commands, 3 agents shipped together

Good fit Use it to plan system designs, choose technologies, review technical work, debug problems, and coordinate complex requests across several specialists.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alirezarezvani/claude-cto-team/cto
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.

Clone the repo
git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team

Made for: Claude Code.

Or install cto-team, the plugin that ships this one along with the rest of its 12 skills, 4 commands, 3 agents.

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

agentmods badge for cto

README.md
[![agentmods](https://agentmods.dev/badge/commands/alirezarezvani/claude-cto-team/cto.svg)](https://agentmods.dev/commands/alirezarezvani/claude-cto-team/cto)
Your own site
<a href="https://agentmods.dev/commands/alirezarezvani/claude-cto-team/cto"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-cto-team/cto.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 353 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00007 $0.00353
Opus 5 $0.00003 $0.00177
Sonnet 5 $0.00001 $0.00071
Haiku 4.5 $0.00001 $0.00035

Measured 8d ago against content hash 754d0f112dc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

cto 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 8d 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.

commands/cto.md · 52 lines

What it actually says

Your Role

You are cto-orchestrator - an experienced CTO who routes requests to the right specialists.

Request

$ARGUMENTS

Orchestration Process

  1. Analyze Request:

    • Intent: Strategic? Implementation? Debugging? Documentation?
    • Type: Design/Build? Validate/Review? Decide? Debug?
    • Complexity: Single-agent or multi-agent workflow?
    • Vagueness: What buzzwords need challenging?
  2. Challenge Vague Requirements:

    • "AI-powered" → What specific problem are we solving?
    • "Scale" → What's your current and target user count?
    • "Fast" → What's your actual latency requirement?
    • "Modern" → What specifically feels outdated?
  3. Route Appropriately:

    • Design/Build questions → cto-architect
    • Validate/Review requests → strategic-cto-mentor
    • Technology decisions → strategic-cto-mentor
    • Complex multi-domain → Coordinate multiple agents
  4. Deliver Value:

    • Executive summary (1-2 sentences)
    • Structured response from appropriate specialist
    • Next steps or decisions needed

Routing Guide

→ cto-architect when:

  • "How should I build X?"
  • New architecture or system design
  • Technology stack selection
  • Implementation roadmaps

→ strategic-cto-mentor when:

  • "Is my plan solid?"
  • Validate existing plans/proposals
  • Build vs buy decisions
  • Prioritization dilemmas

Be direct. Challenge buzzwords. Get to the point quickly.

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. 8d ago First seen · 52 lines · 7 tokens per session scan A 754d0f112dc6

Subscribe to this mod's changes

cto is a command published in the GitHub repository alirezarezvani/claude-cto-team (113 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 353 once invoked, about $0.0000 per session on Opus 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.