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/rito-w/claude-code-best-practice-zh/development-workflowsgit clone --depth 1 https://github.com/Rito-w/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/rito-w/claude-code-best-practice-zh/development-workflows)<a href="https://agentmods.dev/commands/rito-w/claude-code-best-practice-zh/development-workflows"><img src="https://agentmods.dev/badge/commands/rito-w/claude-code-best-practice-zh/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.00017 | $0.04038 |
| Opus 5 | $0.00009 | $0.02019 |
| Sonnet 5 | $0.00003 | $0.00808 |
| Haiku 4.5 | $0.00002 | $0.00404 |
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 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.
This is a copy
100% identical to development-workflows — 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow — Development Workflows
Update the DEVELOPMENT WORKFLOWS table in README.md by researching 11 repos in parallel. Launch agents, merge results, present changes, update table if approved.
The 11 Repos
| # | Repo | Owner |
|---|---|---|
| 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 CEO) |
| 8 | bmad-code-org/BMAD-METHOD |
BMAD Code Org |
| 9 | EveryInc/compound-engineering-plugin |
Every.to |
| 10 | Yeachan-Heo/oh-my-claudecode |
Yeachan Heo (@bellman_ych) |
| 11 | mattpocock/skills |
Matt Pocock |
Table Format
The README table has these columns:
| Name | ★ | Workflow | <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)— use project name, not owner/repo - ★: Star count rounded to
k(e.g., 98k, 10k, 4.1k). Under 1000 show exact number - Workflow: The canonical end-to-end pipeline as a flat left-to-right sequence of shields.io badges joined by
→. Each step is the actual command/skill/agent name from the repo (e.g./speckit.plan,bmad-create-prd,subagent-driven-development). Flat only — no parentheticals, no English qualifiers ("loop", "per story", "parallel waves"), no+connectors. If a step has internal sub-steps that matter, list them as siblings in the main chain and color them yellow (fff3b0) to mark them as sub-loops; top-level steps stay light blue (ddf4ff). Trace the README's "how to use" / "workflow" section for the canonical happy path: idea → spec/plan → tasks → implement → review → ship. - Agent/Command/Skill counts: Just the number (e.g.,
25,0,108+)
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 · 253 lines · 17 tokens per session scan A dec867346454
development-workflows is a command published in the GitHub repository Rito-w/claude-code-best-practice-zh (10 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 4,038 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 development-workflows, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
sync-linear
Sync current work with Linear ticket status.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.