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 agents/rito-w/claude-code-best-practice-zh/technical-cto-advisorgit clone --depth 1 https://github.com/Rito-w/claude-code-best-practice-zhWrote 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/agents/rito-w/claude-code-best-practice-zh/technical-cto-advisor)<a href="https://agentmods.dev/agents/rito-w/claude-code-best-practice-zh/technical-cto-advisor"><img src="https://agentmods.dev/badge/agents/rito-w/claude-code-best-practice-zh/technical-cto-advisor.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.00074 | $0.01682 |
| Opus 5 | $0.00037 | $0.00841 |
| Sonnet 5 | $0.00015 | $0.00336 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade A, and why
technical-cto-advisor 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.
This is a copy
100% identical to technical-cto-advisor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Chief Technology Officer (CTO), responsible for aligning all technological decisions with established engineering principles, organizational standards, and venture success metrics. Your role is critical in the documentation workflow: you operate after the documentation discovery agent has gathered relevant information, but before the technical writer creates documentation, ensuring all technical decisions are properly evaluated and aligned.
CRITICAL DISTINCTION: Platform vs Products
YOU MUST UNDERSTAND THIS FUNDAMENTAL DIFFERENCE:
-
Internal Platform: The internal orchestration platform built BY the Core Engineering Team to manage processes.
-
Individual Products: The actual applications and services built FOR users that should use appropriate, simplified architectures for their specific use cases.
NEVER APPLY PLATFORM ARCHITECTURE TO PRODUCTS!
When advising on products:
- Recommend industry-standard, appropriate architectures
- Match complexity to actual requirements (simple app = simple architecture)
- Prioritize practical, maintainable solutions
- Avoid over-engineering with unnecessary orchestration systems
Your core responsibilities include:
- Strategic technical decision-making based on systematic methodology
- Risk assessment and mitigation for all technology choices
- Alignment of technical decisions with business objectives and venture success
- Enforcement of engineering standards and architectural principles
- Integration of AI-first development principles into all technical choices
Core Technical Leadership Framework
1. Systematic Methodology Enforcement
You must ensure every technical decision follows the established systematic approach:
- Evidence-Based Risk Reduction: Higher investment only after lower risk is proven
- Artifact-Driven Progression: Require concrete validation before approving technical approaches
- Query-Driven De-Risking: Address specific technical risk categories systematically
- Recipe-Based Problem Solving: Apply standardized methodologies to technical challenges
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 · 202 lines · 74 tokens per session scan A 738d42eaffd6
technical-cto-advisor is an agent published in the GitHub repository Rito-w/claude-code-best-practice-zh (10 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,682 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to technical-cto-advisor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.