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 skills/xiaobei930/cc-best/architecturenpx skills add xiaobei930/cc-best --skill architecturegit 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/skills/xiaobei930/cc-best/architecture)<a href="https://agentmods.dev/skills/xiaobei930/cc-best/architecture"><img src="https://agentmods.dev/badge/skills/xiaobei930/cc-best/architecture.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.00029 | $0.01456 |
| Opus 5 | $0.00015 | $0.00728 |
| Sonnet 5 | $0.00006 | $0.00291 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
architecture 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
架构设计技能
本技能提供架构设计的完整指南，包括 ADR 记录、设计检查清单、可扩展性评估、架构模式速查等最佳实践。
子文件
- lead-methodology.md - Lead 角色方法论（技术设计、任务分解）
- pm-methodology.md - PM 角色方法论（需求分析、决策框架）
架构决策记录 (ADR)
对于重要的架构决策，创建 ADR 记录：
ADR 模板 (docs/decisions/ADR-XXX.md)
# ADR-XXX: [决策标题]
## 状态
Proposed | Accepted | Deprecated | Superseded by ADR-YYY
## 上下文
[描述导致这个决策的背景、问题或需求]
## 决策
[明确说明做出的决策]
## 理由
[解释为什么选择这个方案]
## 备选方案
### 方案 A: [名称]
- 优点: ...
- 缺点: ...
### 方案 B: [名称]
- 优点: ...
- 缺点: ...
## 后果
### 正面
- [好处1]
- [好处2]
### 负面
- [代价1]
- [代价2]
### 风险
- [风险1] → 缓解: [措施]
## 相关决策
- ADR-XXX: [相关决策]
## 日期
YYYY-MM-DD
何时创建 ADR
| 场景 | 是否需要 ADR |
|---|---|
| 选择主要技术栈（框架、数据库） | ✅ 必须 |
| 定义核心架构模式 | ✅ 必须 |
| 引入新的外部依赖 | ⚠️ 视影响范围 |
| API 设计重大变更 | ✅ 必须 |
| 简单的实现细节 | ❌ 不需要 |
系统设计检查清单
设计方案前，检查以下维度：
功能性需求
- 用户故事是否清晰完整
- API 契约是否定义明确
- 数据模型是否满足需求
- 边界条件是否考虑
非功能性需求
- 性能: 响应时间目标？吞吐量要求？
- 可扩展性: 预期用户量？数据增长？
- 可用性: 可接受的停机时间？
- 安全性: 认证授权？数据保护？
技术设计
- 架构图是否清晰
- 组件职责是否明确
- 数据流是否完整
- 错误处理策略是否定义
- 测试策略是否规划
运维考虑
- 部署策略是否明确
- 监控告警是否规划
- 日志策略是否定义
- 回滚方案是否准备
可扩展性评估
扩展阶段规划
| 阶段 | 用户量 | 架构要求 |
|---|---|---|
| MVP | <1K | 单体应用足够 |
| 成长期 | 1K-10K | 优化数据库查询，添加缓存 |
| 扩展期 | 10K-100K | 服务拆分，读写分离 |
| 规模化 | >100K | 微服务，分布式缓存，多区域 |
常见瓶颈与解决方案
| 瓶颈 | 解决方案 |
|---|---|
| 数据库读取慢 | 索引优化 → 读写分离 → 缓存层 |
| API 响应慢 | 异步处理 → 消息队列 → CDN |
| 内存不足 | 分页加载 → 流式处理 → 扩容 |
| 并发冲突 | 乐观锁 → 分布式锁 → 事件溯源 |
架构模式速查
后端模式
| 模式 | 适用场景 | 复杂度 |
|---|---|---|
| 分层架构 | 大多数 CRUD 应用 | 低 |
| 六边形架构 | 需要高可测试性 | 中 |
| CQRS | 读写负载差异大 | 高 |
| 事件溯源 | 需要完整审计轨迹 | 高 |
| 微服务 | 团队多、规模大 | 高 |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 209 lines · 29 tokens per session scan A a2ae4f728585
architecture is a skill published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,456 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 skills, from other repositories
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
eval-hooks
Audit Claude Code hooks defined in settings.json files for validity, performance safety, and correctness. Resolves each command against the filesystem, checks exit-code strategy for blocking hooks, flags missing timeouts, and reviews interactive vs async patterns. Use when setting up hooks for the first time…