claude-cto-team: Instructions file for Claude Code

CLAUDE.md

claude-cto-team CLAUDE.md is an instructions file for Claude Code from alirezarezvani/claude-cto-team. It costs 1,517 tokens per session, scanned A, original, MIT.

Project instructions for a Claude Code system made of three specialized agents: a coordinator, an architecture designer, and a technical validator. They explain the system's roles and how the agents work together.

In plain words
What is it for?
Use them to clarify requirements, delegate architecture work, create technical roadmaps, and challenge plans before implementation.
Why use it?
They separate planning, system design, and critical review so technical decisions are routed to the appropriate role.

Instructions file for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

This is alirezarezvani/claude-cto-team's own configuration. It tells Claude Code how to work on claude-cto-team itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-cto-team configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alirezarezvani/claude-cto-team. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alirezarezvani/claude-cto-team/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team

Made for: Claude Code.

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 claude-cto-team CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alirezarezvani/claude-cto-team/claude-md/github.svg)](https://agentmods.dev/instructions/alirezarezvani/claude-cto-team/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/alirezarezvani/claude-cto-team/claude-md"><img src="https://agentmods.dev/badge/instructions/alirezarezvani/claude-cto-team/claude-md/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.

agentmods 80×15 button for claude-cto-team CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/alirezarezvani/claude-cto-team/claude-md"><img src="https://agentmods.dev/badge/instructions/alirezarezvani/claude-cto-team/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,517 This file is loaded in full into every session.
When invoked 1,517 The same file — it is already loaded in full.
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.01517 $0.01517
Opus 5 $0.00758 $0.00758
Sonnet 5 $0.00303 $0.00303
Haiku 4.5 $0.00152 $0.00152

Measured 9d ago against content hash 41b6d174e66f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

claude-cto-team CLAUDE.md 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 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.

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.

CLAUDE.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

This repository implements a "CTO Team" system for Claude Code - a set of three specialized subagents that work together to provide strategic technical leadership, architecture design, and ruthless validation of plans and decisions.

Agent System Architecture

The CTO Team operates as a three-agent system with clear role separation:

┌─────────────────────────────────────────────────────────────────┐
│                     cto-orchestrator                            │
│              (Coordinator & Task Router)                        │
│    Clarifies requirements, challenges vagueness, routes work    │
└─────────────────────┬───────────────────────┬───────────────────┘
                      │                       │
                      ▼                       ▼
┌─────────────────────────────────┐  ┌─────────────────────────────┐
│        cto-architect            │  │   strategic-cto-mentor      │
│    (Forward-Looking Designer)   │  │   (Ruthless Validator)      │
│  Designs systems & roadmaps     │  │  Challenges & stress-tests  │
└─────────────────────────────────┘  └─────────────────────────────┘

Agents

cto-orchestrator

Role: Coordinator and intelligent task router Model: Sonnet (fast, efficient)

The orchestrator is the entry point for complex technical requests. It:

  • Challenges vague requirements ("AI-powered" → what problem exactly?)
  • Clarifies business goals and constraints before delegating
  • Routes to design (cto-architect) or validation (strategic-cto-mentor)
  • Coordinates multi-agent workflows for complex projects
  • Synthesizes outputs from multiple agents

When to use: Vague requirements, multi-domain projects, unclear where to start

cto-architect

Role: Forward-looking system designer Model: Opus (comprehensive, thorough)

The architect designs new systems from scratch. Expertise includes:

  • Full-stack architecture (React, Node.js, mobile, microservices)
  • ML/AI integration (CV pipelines, model serving, RAG systems)
  • Cloud infrastructure (Kubernetes, AWS/GCP, auto-scaling)
  • Technology stack selection with explicit trade-off analysis
  • Phased implementation roadmaps with validation checkpoints

Read the full file on GitHub · 174 lines

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. 9d ago First seen · 174 lines · 1,517 tokens per session scan A 41b6d174e66f

Subscribe to this mod's changes

claude-cto-team CLAUDE.md is an instructions file published in the GitHub repository alirezarezvani/claude-cto-team (113 stars, last pushed 8mo ago), licensed MIT. It adds 1,517 tokens to every session, about $0.0076 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.

Related

Other instructions, from other repositories

vibe-coding-prompt-template backend.instructions.md

Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.

KhazP/vibe-coding-prompt-template · 139 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens