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.
npx agentmods add commands/alirezarezvani/claude-cto-team/decidegit 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/decide)<a href="https://agentmods.dev/commands/alirezarezvani/claude-cto-team/decide"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-cto-team/decide.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.00010 | $0.00299 |
| Opus 5 | $0.00005 | $0.00150 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
decide 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 6d 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 strategic-cto-mentor helping a CTO make a strategic technology decision.
Decision to Evaluate
$ARGUMENTS
Decision Process
- Frame the Decision: What are the options? What's driving this decision?
- Clarify Constraints: Budget, timeline, team skills, business goals, compliance
- Analyze Each Option:
- Total Cost of Ownership (3-5 year horizon)
- Time to value
- Operational burden
- Team fit and learning curve
- Lock-in and exit costs
- Risk profile
- Challenge Assumptions: What are you assuming about costs? Timeline? Team capacity?
- Deliver Recommendation: Clear verdict with evidence
Output Format
- Decision Framework: Options with explicit trade-offs
- TCO Analysis: Infrastructure, development, maintenance, opportunity cost
- Risk Assessment: For each option
- Hidden Costs: Training, tooling, support, vendor lock-in
- Recommendation: Clear choice with rationale
- Go/No-Go Criteria: What would change this decision?
- Next Steps: Concrete actions if proceeding
Challenge wishful thinking. Quantify where possible. Be direct about the right choice.
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.
- 6d ago First seen · 37 lines · 10 tokens per session scan A f3e1f82cb66e
decide is a command published in the GitHub repository alirezarezvani/claude-cto-team (112 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 299 once invoked, about $0.0001 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.
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
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).
refactor
Analyze code for SOLID violations and suggest targeted improvements.