claude-code-best-practice is a repository of agents, commands, skills, hooks, plugins, and configuration guidance for Claude Code. It helps developers organize repeatable workflows and apply agentic engineering practices, including in monorepos. The catalogue entries are its reusable Claude Code workflow components.
Borrowing it
Nothing to install: this file belongs to shanraisshan/claude-code-best-practice. 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/shanraisshan/claude-code-best-practice/main/.claude/commands/workflows/development-workflows.mdgit clone --depth 1 https://github.com/shanraisshan/claude-code-best-practiceWrote 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/shanraisshan/claude-code-best-practice/development-workflows)<a href="https://agentmods.dev/commands/shanraisshan/claude-code-best-practice/development-workflows"><img src="https://agentmods.dev/badge/commands/shanraisshan/claude-code-best-practice/development-workflows/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/shanraisshan/claude-code-best-practice/development-workflows"><img src="https://agentmods.dev/badge/commands/shanraisshan/claude-code-best-practice/development-workflows.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.04038 |
| Opus 5.5 | $0.00007 | $0.01615 |
| Sonnet 5.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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- development-workflows — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 253 lines · 17 tokens per session scan A dec867346454
development-workflows is a command published in the GitHub repository shanraisshan/claude-code-best-practice (68,074 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 4,038 once invoked, about $0.0001 per session on Opus 5.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
README
Git workflow and quality assurance commands for the claude-skills repository.
cs-grill-agent-launcher
Matt Pocock docs-anchored grill for an agent-launcher goal — walks the phase's forcing questions ONE at a time, each with a recommended answer and a citation to a reference doc, refusing to advance on a fuzzy input. Use to pressure-test a CMA plan before launching.
plan-feature
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
statusbar-style
Switch the status-bar look (aurora blocks / aurora thin / classic).
version
Display current guide and Claude Code versions.