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/iterategit 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/commands/xiaobei930/cc-best/iterate)<a href="https://agentmods.dev/commands/xiaobei930/cc-best/iterate"><img src="https://agentmods.dev/badge/commands/xiaobei930/cc-best/iterate.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.00011 | $0.02688 |
| Opus 5 | $0.00005 | $0.01344 |
| Sonnet 5 | $0.00002 | $0.00538 |
| Haiku 4.5 | $0.00001 | $0.00269 |
Grade A, and why
iterate 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/iterate - 自主迭代循环
核心规则: 任务完成后 立即 开始下一个任务，禁止 输出总结后等待用户。
单 session 内的自主开发循环。适合日常开发，在上下文窗口允许的范围内连续完成多个任务。
💡 需要长时间运行（小时级）？请直接使用
/cc-best:cc-ralph命令，参考.claude/ralph-prompts/下的模板。
核心流程
┌─────────────────────────────────────────────────────────────────┐
│ 自主迭代循环 │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 读取 progress.md → 选取任务 → 执行 → 验证 → 提交 → 更新文档 │
│ ↑ │ │
│ └──────────────────────────────────────────────┘ │
│ 自动继续下一任务 │
│ │
└─────────────────────────────────────────────────────────────────┘
立即开始执行：
- 读取
memory-bank/progress.md - 确定当前任务
- 按下方流程执行
执行流程
Step 0: 检查运行模式
读取 memory-bank/config.json（如不存在，默认 full 模式）：
| 模式 | 管线 | 适用场景 |
|---|---|---|
full |
PM → Lead → Designer → Dev → QA | 完整项目开发 |
lite |
Dev → Verify → Commit | 快速编码、小改动 |
Lite 模式: 跳过 Step 1 的角色判断，直接进入 Dev：
- 无需求文档 → 直接
/cc-best:dev - 完成后 →
/cc-best:verify→/cc-best:commit→ 下一任务 - 不执行 PM、Lead、Designer、QA 角色
- 适合已有明确需求的快速编码场景
切换模式:
/cc-best:setup --interactive或直接编辑memory-bank/config.json
Full 模式: 按 Step 1 的角色判断表执行完整管线。
Step 1: 确定角色
| 当前状态 | 选择角色 | 动作 |
|---|---|---|
| 无需求文档 | /cc-best:pm |
需求分析 |
| REQ 有待澄清项（≥1 个低置信度决策） | /cc-best:clarify |
需求澄清 |
| 有需求无设计 | /cc-best:lead |
技术设计 |
| 有设计，前端任务未设计 | /cc-best:designer |
UI 设计指导 |
| 有任务待开发 | /cc-best:dev |
编码实现 |
| 有代码待验证 | /cc-best:verify |
综合验证（构建+类型+Lint+测试+安全） |
| 验证通过，待功能验收 | /cc-best:qa |
功能验收 |
| QA 通过，full 模式，3+ 文件修改 | code-simplifier Agent | 独立上下文审查 AI slop（自动跳过 lite/hotfix） |
| QA 发现实现 Bug（fix_count < 3） | /cc-best:dev --bugfix |
修复后重新 /cc-best:verify → /cc-best:qa |
| QA 修复循环达上限（fix_count >= 3） | /cc-best:lead |
🛑 熔断，重新评审技术方案 |
| QA 发现高影响需求假设错误 | /cc-best:pm |
重新评审需求假设 |
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 · 275 lines · 11 tokens per session scan A 30c9033b3636
iterate is a command published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 2,688 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
validate
You are the quality gate. Your job is to verify that a phase's implementation meets quality standards before the team moves to the next phase. No phase should advance until validation passes.
implement
You are the phase dispatcher. Your job is to route implementation work to the correct phase agent with the right context.
phased-plan
You are generating a 7-phase implementation plan that maps a user story to the structured development workflow.
retro
You are generating a retrospective report for a completed feature. Your job is to analyze git history and project artifacts to surface patterns, measure delivery quality, and suggest workflow improvements.
progress
You are generating a visual progress report showing which phases are complete, in-progress, or pending for the current feature.
commit
You are creating a conventional commit scoped to the current phase of work.