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.
npx skills add fengshao1227/ccg-workflow --skill verify-changegit 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/skills/fengshao1227/ccg-workflow/verify-change)<a href="https://agentmods.dev/skills/fengshao1227/ccg-workflow/verify-change"><img src="https://agentmods.dev/badge/skills/fengshao1227/ccg-workflow/verify-change/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/skills/fengshao1227/ccg-workflow/verify-change"><img src="https://agentmods.dev/badge/skills/fengshao1227/ccg-workflow/verify-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.01057 |
| Opus 5 | $0.00032 | $0.00528 |
| Sonnet 5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
verify-change 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 10d 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
2 near-identical copies found in the catalogue:
- verify-change — 100% identical, 0 lines differ
- verify-change — 100% identical, 0 lines differ
What it actually says
⚖ 校验关卡 · 变更校验
核心原则
变更 = 代码改动 + 文档更新 + 理由记录
无理由的变更是隐患，无记录的变更是灾难
每一次变更都是历史，每一个决策都要留痕
自动分析
运行变更分析脚本（跨平台）：
# 在 skill 目录下运行
node scripts/change_analyzer.js # 分析工作区变更（默认）
node scripts/change_analyzer.js --mode staged # 分析暂存区变更
node scripts/change_analyzer.js --mode committed # 分析已提交变更
node scripts/change_analyzer.js -v # 详细模式
node scripts/change_analyzer.js --json # JSON 输出
检测能力
自动检测项
| 检测项 | 说明 |
|---|---|
| 文件分类 | 自动识别代码/文档/测试/配置文件 |
| 模块识别 | 识别受影响的模块 |
| 文档同步 | 检测代码变更是否同步更新文档 |
| 测试覆盖 | 检测代码变更是否有对应测试 |
| 影响评估 | 评估变更规模和影响范围 |
触发警告的情况
- ⚠️ 代码变更 > 50 行但 DESIGN.md 未更新
- ⚠️ 代码变更 > 30 行但无测试更新
- ⚠️ 新增文件但 README.md 未更新
- ⚠️ 配置文件变更未记录
- ℹ️ 删除文件需确认引用已清理
变更前置检查
在修改任何模块前，必须：
- 读取 README.md — 理解模块定位
- 读取 DESIGN.md — 理解现有决策
- 评估影响范围 — 此变更影响哪些部分
- 确认变更理由 — 为什么要改
变更后置检查
代码修改完成后，必须：
README.md 更新检查
- 模块职责是否变化 → 更新职责描述
- 依赖关系是否变化 → 更新依赖说明
- 使用方式是否变化 → 更新示例代码
DESIGN.md 更新检查
- 新增设计决策 → 记录决策及理由
- 修改现有设计 → 记录变更及原因
- 引入新限制 → 更新已知限制
- 添加变更记录 → 更新变更历史
变更记录格式
在 DESIGN.md 的变更历史中添加：
## 变更历史
### [日期] - [变更标题]
**变更内容**: 简述改了什么
**变更理由**: 为什么要改
**影响范围**: 影响哪些功能/模块
**决策依据**: 为何选择此方案（如适用）
自动触发时机
| 场景 | 触发条件 |
|---|---|
| 设计级变更 | 修改架构、接口、数据结构 |
| 重构完成 | 重构任务完成时 |
| 代码变更 > 30 行 | 较大规模代码修改 |
| 提交前 | 代码提交前检查 |
校验流程
1. 运行 change_analyzer.js 自动分析
2. 识别变更文件和受影响模块
3. 检查文档同步状态
4. 评估变更影响
5. 输出变更校验报告
校验报告格式
## 变更校验报告
### 变更概览
- 变更文件数: N
- 代码变更行数: +X / -Y
- 受影响模块: [模块列表]
### 文档同步状态
- README.md: ✓ 已同步 / ⚠️ 需更新
- DESIGN.md: ✓ 已同步 / ⚠️ 需更新
### 测试覆盖
- 测试文件变更: ✓ 有 / ⚠️ 无
### 结论
可提交 / 需补充文档后提交
What ships with it
1 file 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.
- 10d ago First seen · 141 lines · 65 tokens per session scan A 689a9c0573f6
verify-change is a skill published in the GitHub repository fengshao1227/ccg-workflow (5,881 stars, last pushed 6d ago), licensed MIT. It adds 65 tokens to every session and 1,057 once invoked, about $0.0003 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
code-review-workflow
Review a change in a fixed order — context, correctness, security, then style — and write feedback that is actionable and ranked by severity. Use when the user asks for a code review, wants a pull request or diff reviewed before merge, asks whether a change is safe to ship, or when the task involves reviewing a patch…
refactoring-workflow
Improve the structure of existing code without changing its behaviour, in small verified steps under a green test suite. Use when the user asks to refactor, clean up, restructure or simplify code, wants to reduce duplication or coupling, is preparing a codebase for a feature it cannot currently accommodate, or when…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by OpenBitFun's unified Review mechanism instead.…
pr-review-canvas
Create a OpenBitFun Canvas for reviewing a pull request, branch diff, or change set with Cursor-style diff cards, review maps, risk callouts, and focused reviewer flow. Use when the user asks for a PR review canvas, diff walkthrough, change-set overview, or visual review summary.