claude-code-best-practice is a repository of agents, commands, skills, hooks, plugins, and configuration guidance for Claude Code. It helps developers organize repeatable workflows and apply agentic engineering practices, including in monorepos. The catalogue entries are its reusable Claude Code workflow components.
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/shanraisshan/claude-code-best-practiceWrote 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/shanraisshan/claude-code-best-practice/technical-cto-advisor)<a href="https://agentmods.dev/agents/shanraisshan/claude-code-best-practice/technical-cto-advisor"><img src="https://agentmods.dev/badge/agents/shanraisshan/claude-code-best-practice/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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- technical-cto-advisor — 100% identical, 0 lines differ
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.
- 8d ago First seen · 202 lines · 74 tokens per session scan A 738d42eaffd6
technical-cto-advisor is an agent published in the GitHub repository shanraisshan/claude-code-best-practice (65,687 stars, last pushed yesterday), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
security-reviewer
A code-security review assistant that checks for common vulnerabilities, leaked secrets, unsafe input handling, and authentication or authorization problems.