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/clxzl/claude-code-best-practice-cn/development-workflowsgit clone --depth 1 https://github.com/clxzl/claude-code-best-practice-cnWrote 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/clxzl/claude-code-best-practice-cn/development-workflows)<a href="https://agentmods.dev/commands/clxzl/claude-code-best-practice-cn/development-workflows"><img src="https://agentmods.dev/badge/commands/clxzl/claude-code-best-practice-cn/development-workflows.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.00021 | $0.03027 |
| Opus 5 | $0.00010 | $0.01514 |
| Sonnet 5 | $0.00004 | $0.00605 |
| Haiku 4.5 | $0.00002 | $0.00303 |
Grade A, and why
development-workflows 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 4d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
工作流 — 开发工作流
通过并行研究 9 个仓库来更新 README.md 中的 DEVELOPMENT WORKFLOWS 表格。启动智能体，合并结果，呈现变更，经批准后更新表格。
9 个仓库
| 序号 | 仓库 | 所有者 |
|---|---|---|
| 1 | github/spec-kit |
GitHub 公司 (John Lam / Den Delimarsky) |
| 2 | Fission-AI/OpenSpec |
Fission-AI (@0xTab) |
| 3 | humanlayer/humanlayer |
HumanLayer (Dex Horthy) |
| 4 | affaan-m/everything-claude-code |
Affaan Mustafa |
| 5 | gsd-build/get-shit-done |
Lex Christopherson |
| 6 | obra/superpowers |
Jesse Vincent |
| 7 | garrytan/gstack |
Garry Tan (YC 总裁) |
| 8 | bmad-code-org/BMAD-METHOD |
BMAD Code Org |
| 9 | EveryInc/compound-engineering-plugin |
Every.to |
表格格式
README 表格包含以下列：
| 名称 | ★ | 独特性 | 计划 | <img src="!/tags/a.svg" height="14"> | <img src="!/tags/c.svg" height="14"> | <img src="!/tags/s.svg" height="14"> |
- Name：
[Short Name](github-url)— 使用项目名称，而非 owner/repo - ★：星标数四舍五入到
k（例如 98k、10k、4.1k）。低于 1000 显示精确数字 - Uniqueness：2-3 个 shields.io 徽章标签，使用
。空格用下划线，连字符用--，+用%2B，/用%2F - Plan：图标 + Plan 实现的链接名称。图标为
<img src="!/tags/c.svg" height="14">表示命令，<img src="!/tags/a.svg" height="14">表示智能体，<img src="!/tags/s.svg" height="14">表示技能。名称链接到仓库中的实际文件 - Agent/Command/Skill 数量：仅数字（例如
25、0、108+）
排序方式：按星标降序排列（最高的在前）。不要按 Plan 类型分组。
阶段 0：读取当前状态
读取以下文件：
README.md—## ⚙️ DEVELOPMENT WORKFLOWS表格（注意当前星标、标签、Plan 链接、数量）changelog/development-workflows/changelog.md— 之前的更新日志条目
阶段 1：启动 2 个研究智能体
立即在单条消息中生成两个智能体（并行）。每个使用 subagent_type: "development-workflows-research-agent"。
智能体 1（3 个仓库）
研究以下 3 个 Claude Code 工作流仓库：
仓库 1：github/spec-kit (https://github.com/github/spec-kit) 仓库 2：affaan-m/everything-claude-code (https://github.com/affaan-m/everything-claude-code) 仓库 3：obra/superpowers (https://github.com/obra/superpowers)
对每个仓库，返回：
- 星标数 — 使用 GitHub API
https://api.github.com/repos/{owner}/{repo}，读取stargazers_count。四舍五入到k。- 智能体数量 — 统计
agents/或.claude/agents/中的.md文件。对于 obra，还统计由技能分派的隐式子智能体。- 技能数量 — 统计
skills/或.claude/skills/中的文件夹。- 命令数量 — 统计
commands/或.claude/commands/中的.md文件。对于 spec-kit，统计templates/commands/中的文件。- Plan 实现 — 找到 Plan/规划智能体、技能或命令。返回其名称、类型（智能体/技能/命令）和文件路径。
- 独特性标签 — 2-3 个短标签（每个 2-3 个词），概括此工作流的独特之处。
- 重要变更 — 有任何重要的近期变更吗？新智能体/技能/命令、主要版本？
每个仓库返回结构化报告：
REPO: github/spec-kit STARS: <number>k AGENTS: <count> COMMANDS: <count> SKILLS: <count> PLAN: <name> (<type>) — <file-path> TAGS: <tag1>, <tag2>, <tag3> CHANGES: <changes or "No significant changes">
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.
- 4d ago First seen · 208 lines · 21 tokens per session scan A 4b3302619982
development-workflows is a command published in the GitHub repository clxzl/claude-code-best-practice-cn (127 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 3,027 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
git
Git operations with intelligent commit messages and workflow optimization.
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.