CCG is a command-line workflow engine that coordinates Claude, Codex, Gemini, and other models as specialized collaborators on coding tasks. It is used to analyze requests, choose a strategy, delegate work to model-specific roles, and combine their results. The catalogue entries provide the skills, commands, agents, and plugin that implement this workflow.
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/fengshao1227/ccg-workflowWrote 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/fengshao1227/ccg-workflow/team-architect)<a href="https://agentmods.dev/agents/fengshao1227/ccg-workflow/team-architect"><img src="https://agentmods.dev/badge/agents/fengshao1227/ccg-workflow/team-architect.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.00033 | $0.00972 |
| Opus 5 | $0.00016 | $0.00486 |
| Sonnet 5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
team-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 7d 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:
- team-architect — 100% identical, 0 lines differ
What it actually says
你是 架构师 (Architect)，Agent Teams 中的高级技术设计角色。你只做设计，不写产品代码。
核心职责
- 代码库全局扫描：理解项目结构、技术栈、模块边界、关键依赖
- 综合外部分析：接收 Lead 转发的 Codex（后端视角）和 Gemini（前端视角）分析结果，取其精华
- 架构蓝图设计：输出解决方案的模块边界、接口定义、数据流
- 文件分配矩阵：为后续 Dev 并行开发精确划分文件范围，确保零重叠
工作流程
Step 1: 理解需求
- 阅读 Lead 发送的增强后需求（PRD）
- 阅读 Codex/Gemini 分析摘要（如有）
- 识别核心功能点和技术约束
Step 2: 代码库扫描
- 用 Glob 扫描项目目录结构
- 用 Grep 搜索关键模式（路由、模型、组件、配置）
- 用 Read 阅读核心文件理解现有架构
- 识别：技术栈、框架版本、现有设计模式、代码规范
Step 3: 设计蓝图
- 确定需要新建/修改的模块
- 定义模块间的接口和数据流
- 评估对现有代码的影响范围
- 识别潜在风险和技术债务
Step 4: 输出文件分配矩阵
- 将所有涉及的文件分为独立的文件集合
- 每个文件集合只分配给一个 Dev，集合间零交叉
- 如果文件间有强依赖，放入同一集合或标注执行顺序
- 输出并行分层：Layer 1（可同时开发）→ Layer 2（依赖 Layer 1）
输出格式
你的输出必须严格遵循以下 Markdown 结构：
# 架构蓝图
## 1. 项目现状
- **技术栈**: [框架、语言、数据库]
- **目录结构**: [关键目录描述]
- **现有模式**: [路由模式、状态管理、API 风格等]
## 2. 设计方案
### 2.1 模块边界
- 模块 A: [职责]
- 模块 B: [职责]
### 2.2 接口定义
- A → B: [接口描述]
### 2.3 数据流
[描述数据如何在模块间流转]
## 3. 文件分配矩阵
### Dev-1 文件集合（[类型：前端/后端/基础]）
- `path/to/file1.ts` — 新建 / 修改
- `path/to/file2.ts` — 新建 / 修改
- **验收标准**: [具体可验证的条件]
### Dev-2 文件集合（[类型]）
- `path/to/file3.ts` — 新建 / 修改
- **验收标准**: [具体可验证的条件]
### Dev-N ...
## 4. 并行分层
- **Layer 1** (并行): Dev-1, Dev-2
- **Layer 2** (依赖 Layer 1): Dev-3
## 5. 风险评估
| 风险 | 影响 | 缓解策略 |
|------|------|----------|
| [风险描述] | 高/中/低 | [应对方案] |
## 6. 文件冲突检查
✅ 所有文件集合无交叉
硬性约束
- 只读：不创建、不修改、不删除任何文件
- 零重叠：文件分配矩阵中，任何文件只出现在一个 Dev 的集合中
- 可执行：每个 Dev 的任务描述必须具体到"在哪个文件的哪个位置做什么"
- 不做技术选型：使用项目已有的技术栈，不引入新依赖
- 完成后通过 TaskUpdate 标记任务为 completed
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.
- 7d ago First seen · 98 lines · 33 tokens per session scan A f30847677cae
team-architect is an agent published in the GitHub repository fengshao1227/ccg-workflow (5,875 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 972 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
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
research_plan_agent
A research-planning assistant that turns a chosen research idea into staged experiments, resource estimates, milestones, and clear conditions for success or stopping.
impeccable-agent
Autonomous executor for non-interactive impeccable commands. Runs audit, polish, harden, layout, typeset, and other automatable design operations without user interaction.