Borrowing it
Nothing to install: this file belongs to BuaaJoseph/claude-code-best-practice-zh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BuaaJoseph/claude-code-best-practice-zh/master/.claude/commands/workflows/best-practice/workflow-claude-commands.mdgit clone --depth 1 https://github.com/BuaaJoseph/claude-code-best-practice-zhWrote 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/buaajoseph/claude-code-best-practice-zh/workflow-claude-commands)<a href="https://agentmods.dev/commands/buaajoseph/claude-code-best-practice-zh/workflow-claude-commands"><img src="https://agentmods.dev/badge/commands/buaajoseph/claude-code-best-practice-zh/workflow-claude-commands/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/commands/buaajoseph/claude-code-best-practice-zh/workflow-claude-commands"><img src="https://agentmods.dev/badge/commands/buaajoseph/claude-code-best-practice-zh/workflow-claude-commands.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.01923 |
| Opus 5 | $0.00009 | $0.00962 |
| Sonnet 5 | $0.00003 | $0.00385 |
| Haiku 4.5 | $0.00002 | $0.00192 |
Grade A, and why
workflow-claude-commands 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 9d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
工作流变更日志 — 命令报告
您是 claude-code-best-practice 项目的协调员。您的工作是启动一个研究 agent，等待它的结果，并呈现一份关于 命令参考报告（best-practice/claude-commands.md）漂移的报告。
此工作流正好检查两种类型的漂移：
- Frontmatter 字段 — 官方文档中添加或移除的任何字段
- 官方命令 — 添加或移除的任何内置斜杠命令
要检查的版本： $ARGUMENTS（如果为空或不是数字，默认为 10）
这是一个先读取后报告的工作流。启动 agent，合并发现，产生报告。只有在用户批准后才采取行动。
阶段 1：启动研究 Agent
使用以下提示生成 workflow-claude-commands-agent：
研究 claude-code-best-practice 项目的命令报告漂移。检查最近 $ARGUMENTS 个版本（默认：10）。
获取这 2 个外部来源：
- 斜杠命令参考：https://code.claude.com/docs/en/slash-commands
- 变更日志：https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
然后读取本地报告（
best-practice/claude-commands.md）。正好检查两件事：
- Frontmatter 字段：将官方文档支持的命令 frontmatter 字段与报告的 Frontmatter Fields 表进行比较。标记任何添加或移除的字段。
- 官方命令：将官方文档的内置斜杠命令列表与报告的 official commands 表进行比较。标记任何添加或移除的命令。还要检查任何命令的标签或描述是否已更改。
阶段 2：读取之前的变更日志条目
在 agent 运行期间，读取 changelog/best-practice/claude-commands/changelog.md 以获取最后 25 个条目。解析优先级操作以识别：
- 重复出现的问题 — 之前出现过但仍未解决的问题
- 新问题 — 首次出现的问题
- 已解决的问题 — 之前标记的问题现在已修复
阶段 3：生成报告
等待 agent 完成。 生成包含以下部分 的报告：
- Frontmatter 字段变更 — 官方文档与我们报告相比添加或移除的字段
- 官方命令变更 — 与我们的表相比添加或移除的内置斜杠命令
以优先的操作项摘要表结束。每个项目必须包含显示 NEW、RECURRING (first seen: <date>) 或 RESOLVED 的 Status 列：
Priority Actions:
# | Type | Action | Status
1 | New Field | Add <field> to frontmatter table | NEW
2 | Removed Field | Remove <field> from table | RECURRING (first seen: <date>)
3 | New Command | Add <command> to official table | NEW
4 | Removed Command | Remove <command> from table | NEW
5 | Changed Tag | Update <command> tag from X to Y | NEW
还要包含一个自上次运行以来已解决部分，列出之前运行中不再是问题的任何项目。
阶段 3.5：将摘要追加到变更日志
此阶段是强制的 — 在向用户呈现报告之前始终执行。
读取现有的 changelog/best-practice/claude-commands/changelog.md 文件，然后追加（不要覆盖）一个新条目在末尾。条目格式必须完全如下：
---
## [<YYYY-MM-DD HH:MM AM/PM PKT>] Claude Code v<VERSION>
| # | Priority | Type | Action | Status |
|---|----------|------|--------|--------|
| 1 | HIGH/MED/LOW | <type> | <action description> | <status> |
| ... | ... | ... | ... | ... |
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.
- 9d ago First seen · 140 lines · 17 tokens per session scan A bfaac6925ce2
workflow-claude-commands is a command published in the GitHub repository BuaaJoseph/claude-code-best-practice-zh (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 1,923 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-31.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.