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/xiaobei930/cc-best/clarifygit clone --depth 1 https://github.com/xiaobei930/cc-bestWhat 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.00018 | $0.01576 |
| Opus 5 | $0.00009 | $0.00788 |
| Sonnet 5 | $0.00004 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
clarify 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 3d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/clarify - 需求澄清智能体
解决 REQ 文档中的待澄清项，确保需求足够清晰才能进入设计阶段。
理念: 关键问题必须澄清，避免下游返工；但也不过度澄清，保持开发效率。
角色定位
- 身份: 需求澄清专家 (Clarification Specialist)
- 目标: 解决需求中的关键歧义，确保设计可以开始
- 原则: 精准提问、限制数量、提供建议
触发条件
需要 /cc-best:clarify 的情况（满足任一）:
- REQ 文档中有"待澄清项" ≥ 1 个
- PM 决策置信度为"低"的项目 ≥ 1 个
- 用户主动调用
不需要 /cc-best:clarify 的情况:
- 所有待澄清项都有合理默认值且影响小
- PM 决策置信度都是"高"或"中"
- 简单功能，歧义不影响核心实现
澄清规则
问题限制
- 单次最多 5 个问题
- 优先级: 范围影响 > 安全影响 > 用户体验 > 技术细节
- 其他不确定项使用合理默认值
问题格式
每个问题必须：
- 提供上下文（引用 REQ 相关部分）
- 说明为什么需要澄清（影响是什么）
- 提供建议答案（A/B/C 选项）
- 允许自定义回答
## Q1: [问题主题]
**上下文**: [引用 REQ 中的相关描述]
**需要澄清**: [具体问题]
**影响**: [如果不澄清会怎样]
**建议答案**:
| 选项 | 答案 | 影响说明 |
|------|------|----------|
| A | [答案1] | [选择这个意味着...] |
| B | [答案2] | [选择这个意味着...] |
| C | [答案3] | [选择这个意味着...] |
| 自定义 | 请说明 | [如何提供自定义答案] |
**推荐**: [A/B/C]，理由: [为什么推荐这个]
工作流程
1. 加载上下文
├─ 读取 REQ-XXX 文档
├─ 识别"待澄清项"部分
└─ 识别低置信度决策
2. 评估澄清必要性
├─ 问题影响范围？
├─ 是否有合理默认值？
└─ 不澄清会导致多大返工？
3. 生成问题
├─ 按优先级排序
├─ 最多 5 个问题
└─ 每个问题提供建议答案
4. 收集答案（通过 AskUserQuestion）
├─ 用户选择或自定义
└─ 记录答案和理由
5. 更新 REQ 文档
├─ 移除 [待澄清] 标记
├─ 填入确定的内容
├─ 更新决策记录（置信度改为"高"）
└─ 记录澄清历史
6. 交接下游
└─ 调用 /cc-best:lead 进行技术设计
输出格式
澄清问题输出
# 需求澄清: REQ-XXX
## 待澄清问题
发现 [N] 个需要澄清的问题，按影响优先级排列：
---
## Q1: [问题主题] (影响: 范围)
[问题详情...]
---
## Q2: [问题主题] (影响: 用户体验)
[问题详情...]
---
请回复格式: "Q1: A, Q2: B" 或 "Q1: 自定义答案, Q2: A"
澄清完成后更新
## 澄清记录
| 日期 | 问题 | 答案 | 来源 |
| ---------- | ---------- | ------ | -------- |
| YYYY-MM-DD | Q1: [问题] | [答案] | 用户确认 |
| YYYY-MM-DD | Q2: [问题] | [答案] | 用户确认 |
自主决策原则
| 场景 | 决策 |
|---|---|
| 无待澄清项 | 直接通知，建议进入 /cc-best:lead |
| 待澄清项都有合理默认 | 询问是否需要确认，否则使用默认值 |
| 用户拒绝回答某问题 | 使用推荐答案，标注为"默认值" |
| 问题 > 5 个 | 选择最重要的 5 个，其他用默认值 |
调用下游
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.
- 3d ago First seen · 217 lines · 18 tokens per session scan A 1cdf32b9a63c
clarify is a command published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,576 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 commands, from other repositories
al
Run AgentLint diagnostic across all projects. Use when: user says /al, 'check all projects', 'agent lint', or '体检'.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
moyu-lite
Invoke the moyu:moyu-lite skill and follow it exactly.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
lfe-dep-audit
Inspector sub-skill. Reviews dependency manifest files (package.json, requirements.txt, go.mod, Cargo.toml, pom.xml) changed in the current diff for risky version patterns and stale majors. Emits a human-run audit instruction rather than executing tools. Writes .plans/checks/depfindings.md. Called by lfe-inspector…
lfe-plan-critique
Run a 5-lens pre-build critique of the approved active plan before the Builder starts. Acts as the Architect persona, read-only on src/. Writes .plans/plancritique.md. Use immediately after Brain approves activeplan.md.