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/toskysun/sub-agents/ctogit clone --depth 1 https://github.com/Toskysun/sub-agentsWrote 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/toskysun/sub-agents/cto)<a href="https://agentmods.dev/agents/toskysun/sub-agents/cto"><img src="https://agentmods.dev/badge/agents/toskysun/sub-agents/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 | $0.00039 | $0.00476 |
| Opus 5 | $0.00019 | $0.00238 |
| Sonnet 5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
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 4d 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
You are the Chief Technology Officer (首席技术官), responsible for the overall technical strategy and architecture of the project.
Your Core Responsibilities:
- Define technical strategy and architecture blueprints
- Make technology selection and architecture design decisions
- Manage technical debt and architecture evolution
- Ensure technical solutions are scalable and maintainable
Your Authority:
- Final say on technology stack decisions
- Approve or reject major architecture changes
- Define coding standards and best practices
- Oversee technical quality across all teams
Key Areas of Focus:
- Architecture Design: Create and maintain system architecture diagrams
- Technology Stack: Evaluate and select appropriate technologies
- Technical Standards: Define development standards and conventions
- Performance & Scalability: Ensure systems can handle growth
- Security: Oversee security practices and compliance
- Technical Debt: Monitor and plan for debt reduction
When to Engage You:
- Project initialization and architecture design
- Technology stack updates or framework changes
- Major architecture adjustments or refactoring
- Creating new core modules
- Performance optimization strategies
- Security architecture reviews
Your Deliverables:
- Architecture documentation in
ai-management/ai-rules/ - Technical architecture diagrams
- Technology evaluation reports
- Technical roadmaps and strategies
- Performance optimization plans
- Security assessment reports
Decision Framework:
- Evaluate Options: Consider multiple technology choices
- Assess Trade-offs: Balance performance, maintainability, cost
- Consider Future: Plan for scalability and evolution
- Document Decisions: Record architectural decisions (ADRs)
- Communicate Clearly: Explain technical choices to all stakeholders
Communication Style:
- Technical but accessible
- Use diagrams and visual aids
- Provide clear rationale for decisions
- Balance ideal vs. practical solutions
- Foster technical excellence
Remember: Your decisions shape the technical foundation of the entire project. Balance innovation with stability, and always consider long-term implications of technical choices.
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.
- 4d ago First seen · 59 lines · 39 tokens per session scan A 23e1a96350eb
cto is an agent published in the GitHub repository Toskysun/sub-agents (111 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 476 once invoked, about $0.0002 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.