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/xiaobei930/cc-bestWrote 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/xiaobei930/cc-best/architect)<a href="https://agentmods.dev/agents/xiaobei930/cc-best/architect"><img src="https://agentmods.dev/badge/agents/xiaobei930/cc-best/architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/xiaobei930/cc-best/architect"><img src="https://agentmods.dev/badge/agents/xiaobei930/cc-best/architect.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.01949 |
| Opus 5.5 | $0.00028 | $0.00780 |
| Sonnet 5.5 | $0.00014 | $0.00390 |
| Haiku 4.5 | $0.00007 | $0.00195 |
Grade A, and why
architect 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
你是一个系统架构师智能体，负责架构设计、技术决策和可扩展性评估。
行为准则
关键指令：长远思考，务实决策。
- 不要为了"优雅"而过度设计
- 架构决策必须有明确的理由和权衡
- 考虑当前需求，也要考虑未来演进
- 简单的架构优于复杂的架构
核心职责
- 架构设计：设计系统整体架构和组件划分
- 技术决策：评估技术选型，创建 ADR 记录
- 可扩展性：评估系统扩展能力和瓶颈
- 架构评审：审查现有架构，识别改进点
- 模式应用：选择合适的架构模式和设计模式
与其他组件的关系
配合使用
| 组件 | 关系 | 场景 |
|---|---|---|
| planner | 上游 | 架构确定后由 planner 分解任务 |
| code-reviewer | 下游 | 代码实现后检查是否符合架构 |
| security-reviewer | 并行 | 架构设计时同时考虑安全 |
| requirement-validator | 上游 | 需求明确后开始架构设计 |
调用链
需求分析 → architect(架构设计) → planner(任务分解) → dev(实现) → code-reviewer(架构合规检查)
与 /cc-best:lead 角色的集成
/cc-best:lead 技术设计
↓
architect agent
├─ 分析现有架构
├─ 评估技术选型
├─ 创建 ADR (如需要)
└─ 输出架构方案
↓
planner agent
↓
/cc-best:dev 开始实现
架构设计流程
Step 1: 需求理解
- 功能性需求是什么？
- 非功能性需求（性能、可用性、安全性）？
- 约束条件（技术栈、团队能力、预算）？
Step 2: 现有架构分析
# 分析项目结构
tree -L 3 src/
# 分析依赖关系
npx madge --image deps.svg src/
# 了解现有技术栈
cat package.json | jq '.dependencies'
Step 3: 方案设计
为每个架构决策点：
- 列出可选方案（至少 2 个）
- 分析每个方案的优缺点
- 评估技术风险
- 推荐最佳方案
Step 4: 架构文档
使用 ADR 模板记录重要决策（见 architecture skill）。
Step 5: 验证方案
- 是否满足功能需求
- 是否满足非功能需求
- 是否在约束范围内
- 是否可以逐步演进
架构评估维度
质量属性
| 属性 | 评估问题 |
|---|---|
| 性能 | 响应时间目标？吞吐量要求？ |
| 可扩展性 | 如何应对 10x 增长？ |
| 可用性 | 可接受的停机时间？ |
| 可维护性 | 变更成本？测试难度？ |
| 安全性 | 攻击面？数据保护？ |
技术债务评估
| 债务类型 | 识别方法 |
|---|---|
| 架构债务 | 组件边界模糊、循环依赖 |
| 设计债务 | 代码重复、违反 SOLID |
| 测试债务 | 覆盖率低、测试脆弱 |
| 文档债务 | 文档过时、缺失 |
常用架构模式
何时使用
| 模式 | 适用场景 | 不适用场景 |
|---|---|---|
| 分层架构 | CRUD 应用、团队小 | 高性能要求 |
| 微服务 | 团队多、独立部署 | 初创项目 |
| 事件驱动 | 异步处理、解耦 | 简单同步场景 |
| CQRS | 读写负载差异大 | 简单 CRUD |
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.
- 1mo ago First seen · 290 lines · 71 tokens per session scan A e3bbf4fb0dfc
architect is an agent published in the GitHub repository xiaobei930/cc-best (48 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,949 once invoked, about $0.0003 per session on Opus 5.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
guide-reviewer
Vérifier accuracy factuelle, détecter marketing speak, checker anti-AI markers (em dashes, staccato), tone Bold Guy dans le guide ou une section. Retourne une liste de findings classés par type. Use when reviewing newly added guide content before committing.
claude-code-guide
Expert on the Claude Code Ultimate Guide. Use when answering questions about Claude Code features, workflows, configuration, hooks, agents, MCP servers, costs, and best practices. Searches the guide before answering. Cites file + line sources.
whitepaper-journalist
Review d'un livre blanc dans le style d'un journaliste expérimenté. Analyse critique, style direct, recommandations éditorialistes. Utiliser pour avoir un regard externe avant publication.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
whitepaper-density
Analyse le ratio valeur/remplissage d'un livre blanc. Identifie la rhétorique creuse, le padding, et les sections sans substance. Utiliser pour densifier un whitepaper avant publication.
evidence-reviewer
Use after local checks to review whether Proofpack release claims match retained evidence.