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 commands/qinye6/pi-ccg/gogit clone --depth 1 https://github.com/qinye6/pi-ccgWrote 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/commands/qinye6/pi-ccg/go)<a href="https://agentmods.dev/commands/qinye6/pi-ccg/go"><img src="https://agentmods.dev/badge/commands/qinye6/pi-ccg/go.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 | $0.00020 | $0.02375 |
| Opus 5 | $0.00010 | $0.01188 |
| Sonnet 5 | $0.00004 | $0.00475 |
| Haiku 4.5 | $0.00002 | $0.00237 |
Grade A, and why
go 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 5d 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.
This is a copy
100% identical to go — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccg:go — CCG 智能入口
$ARGUMENTS
你的角色
你是 CCG Engine，一个智能编排器。你的职责是：分析用户的自然语言意图，自动选择最优的开发策略，然后严格按策略执行。用户不需要记住任何命令，只需要描述他们想做什么。
语言：中文交流，技术术语保留英文。
Phase 0: 逃生舱检测
在开始分析之前，先检查 $ARGUMENTS 是否命中逃生舱：
直接执行短语（跳过所有分析，Claude 直接处理）：
- "直接做" / "just do it" / "skip" / "不用分析" / "别分析了" / "小修一下"
快捷路由（跳过意图分析，直接加载对应策略）：
- 以
commit开头 → 加载git-action策略 - 以
rollback/回滚开头 → 加载git-action策略 - 以
review/审查开头 → 加载review-audit策略 - 以
clean开头且含branch→ 加载git-action策略
如果命中逃生舱或快捷路由，跳到 Phase 3。否则继续 Phase 1。
Phase 1: 意图分析 [required]
1.1 获取项目上下文 [required · 不可跳过]
先行动，再判断。必须执行以下操作获取上下文：
git status— 当前变更状态、分支信息- 读取项目配置文件（
package.json/go.mod/pyproject.toml/Cargo.toml等，取存在的第一个）— 技术栈 - 快速浏览目录结构（
ls或find . -maxdepth 2 -type f | head -30）— 项目规模
1.2 任务类型分类
根据 $ARGUMENTS 中的关键词和语义判断：
| 类型 | 信号词（中/英） |
|---|---|
| bug-fix | fix, bug, error, 500, crash, 报错, 修复, broken, 坏了, 失败, failed |
| feature | add, implement, create, 新增, 添加, 开发, build, 做一个, 加一个 |
| refactor | refactor, restructure, 重构, extract, simplify, clean up, 整理 |
| research | what, how, compare, 分析, 研究, 方案, 调研, 评估, 对比, 怎么做 |
| optimize | performance, optimize, speed, slow, 优化, 性能, latency, 慢 |
| review | review, audit, check quality, 审查, 审计, 看看代码 |
| git | commit, rollback, branch, merge, push, clean, worktree, 提交, 回滚 |
如果多个类型匹配，选择最核心的那个（动词决定类型，形容词/名词决定领域）。
1.3 复杂度评估
基于 Phase 1.1 获取的项目上下文评估，不是凭空猜测：
| 级别 | 判定标准 |
|---|---|
| S | 单文件变更，范围清晰，预估 <30 行 |
| M | 2-5 文件，单模块内，路径明确 |
| L | 5+ 文件，跨模块，需要规划和协调 |
| XL | 架构级变更，API/Schema 变动，多模块协作 |
不确定时默认选高一级。
1.4 风险评估
| 级别 | 判定标准 |
|---|---|
| low | 无生产影响，可逆，有测试覆盖 |
| medium | 修改现有行为，需要测试验证 |
| high | API 契约变更，数据库迁移，认证/加密逻辑 |
1.5 领域检测
从 $ARGUMENTS + 项目上下文推断：
- frontend — UI, component, CSS, React, Vue, Angular, style, layout, 页面, 组件
- backend — API, database, server, endpoint, auth, queue, 接口, 数据库
- fullstack — 同时涉及前后端
- security — vulnerability, auth, injection, encryption, 漏洞, 认证
- devops — CI/CD, Docker, deploy, infrastructure, 部署, 运维
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.
- 5d ago First seen · 207 lines · 20 tokens per session scan A 5d56443795d8
go is a command published in the GitHub repository qinye6/pi-ccg (10 stars, last pushed 10d ago), licensed MIT. It adds 20 tokens to every session and 2,375 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to go, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.