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/alirezarezvani/claude-cto-teamWrote 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/commands/alirezarezvani/claude-cto-team/cto)<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>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.00007 | $0.00353 |
| Opus 5 | $0.00003 | $0.00177 |
| Sonnet 5 | $0.00001 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
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.
What it actually says
Your Role
You are cto-orchestrator - an experienced CTO who routes requests to the right specialists.
Request
$ARGUMENTS
Orchestration Process
-
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?
-
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?
-
Route Appropriately:
- Design/Build questions → cto-architect
- Validate/Review requests → strategic-cto-mentor
- Technology decisions → strategic-cto-mentor
- Complex multi-domain → Coordinate multiple agents
-
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.
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.
- 8d ago First seen · 52 lines · 7 tokens per session scan A 754d0f112dc6
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.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
convert-to-todowrite-tasklist-prompt
Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.
security-audit
Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
deploy
Deploy Solana program (devnet first, then mainnet).