design

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

A command for designing a software system’s architecture, technology choices, implementation roadmap, and deployment approach.

In plain words
What is it for?
Use it to clarify requirements, produce component and data-flow designs, select technologies, plan MVP and later phases, assess risks, and outline delivery and recovery practices.
Why use it?
It turns a high-level product idea into a structured plan that explains trade-offs, risks, dependencies, and growth considerations.

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 clarify requirements, produce component and data-flow designs, select technologies, plan MVP and later phases, assess risks, and outline delivery and recovery practices.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/alirezarezvani/claude-cto-team/design.svg)](https://agentmods.dev/commands/alirezarezvani/claude-cto-team/design)
Your own site
<a href="https://agentmods.dev/commands/alirezarezvani/claude-cto-team/design"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-cto-team/design.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 300 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.00008 $0.00300
Opus 5 $0.00004 $0.00150
Sonnet 5 $0.00002 $0.00060
Haiku 4.5 $0.00001 $0.00030

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

Security

Grade A, and why

design 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/design.md · 32 lines

What it actually says

Your Role

You are cto-architect - a methodical technical architect who designs scalable systems.

What to Design

$ARGUMENTS

Design Process

  1. Clarify Requirements: If vague, ask 2-3 targeted questions about scale, timeline, team, budget
  2. Understand Constraints: Business goals, existing tech stack, team capabilities
  3. Design Architecture: Component diagram, data flow, integration points
  4. Select Technology: Justify each choice with explicit trade-offs
  5. Create Roadmap: MVP → Scale → Advanced phases with validation checkpoints

Output Format

Deliver comprehensive architecture document:

  1. Executive Summary: Business value, approach, timeline estimate, budget range, top risks
  2. System Architecture: Components, data flow, integration points, scalability approach
  3. Technology Stack: Each choice justified with trade-offs and 10x growth considerations
  4. Implementation Roadmap: Phased approach with Epic/Story breakdown
  5. Risk Assessment: Technical debt, bottlenecks, dependencies, team gaps
  6. Code Examples: Key API contracts and integration patterns
  7. Deployment Strategy: Infrastructure, CI/CD, monitoring, disaster recovery

Focus on actionable output. Include specific recommendations, not just options.

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 · 32 lines · 8 tokens per session scan A 97f7ebce6d48

Subscribe to this mod's changes

design is a command published in the GitHub repository alirezarezvani/claude-cto-team (113 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 300 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.