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/workflow-conceptsgit 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/workflow-concepts)<a href="https://agentmods.dev/commands/rito-w/claude-code-best-practice-zh/workflow-concepts"><img src="https://agentmods.dev/badge/commands/rito-w/claude-code-best-practice-zh/workflow-concepts.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.1 | $0.00015 | $0.03091 |
| Opus 5 | $0.00008 | $0.01545 |
| Sonnet 5 | $0.00003 | $0.00618 |
| Haiku 4.5 | $0.00002 | $0.00309 |
Grade A, and why
workflow-concepts 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 6d 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 workflow-concepts — 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Changelog — README Concepts
You are a coordinator for the claude-code-best-practice project. Your job is to launch two research agents in parallel, wait for their results, merge findings, and present a unified report about drift in the README CONCEPTS section (README.md).
Versions to check: $ARGUMENTS (default: 10 if empty or not a number)
This is a read-then-report workflow. Launch agents, merge results, and produce a report. Only take action if the user approves.
Phase 0: Launch Both Agents in Parallel
Immediately spawn both agents using the Task tool in the same message (parallel launch):
Agent 1: workflow-concepts-agent
Spawn using subagent_type: "workflow-concepts-agent". Give it this prompt:
Research the claude-code-best-practice project for README CONCEPTS section drift. Check the last $ARGUMENTS versions (default: 10).
Fetch these 3 external sources:
- Claude Code Docs Index: https://code.claude.com/docs/en
- Claude Code Changelog: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
- Claude Code Features Overview: https://code.claude.com/docs/en/overview
Then read the local README.md (specifically the CONCEPTS table), CLAUDE.md, and
reports/claude-global-vs-project-settings.md. Analyze differences between what the official docs list as Claude Code concepts/features and what our README CONCEPTS table documents. Return a structured findings report covering missing concepts, changed concepts, deprecated concepts, URL accuracy, description accuracy, and badge accuracy.
Agent 2: claude-code-guide
Spawn using subagent_type: "claude-code-guide". Give it this prompt:
Research the latest Claude Code features and concepts. I need you to find the COMPLETE list of all Claude Code concepts/features that should be documented. For each, provide:
- Official feature name
- Official docs URL
- File system location (e.g.,
.claude/commands/,~/.claude/teams/)- Brief description (one line)
- When it was introduced (version/date if known)
Specifically check for these potentially missing concepts:
- Worktrees — git worktree isolation for parallel development
- Agent Teams — multi-agent coordination
- Tasks — persistent task lists across sessions
- Auto Memory — Claude's self-written project learnings
- Keybindings — custom keyboard shortcuts
- Remote Connections — SSH, Docker, cloud development
- IDE Integration — VS Code, JetBrains extensions
- Model Configuration — model selection and routing
- GitHub Integration — PR reviews, issue triage
- Any other concept from recent Claude Code versions
Be thorough — search the web, fetch docs, and provide concrete version numbers and details for everything you find.
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.
- 6d ago First seen · 233 lines · 15 tokens per session scan A 4c912b61933a
workflow-concepts 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 15 tokens to every session and 3,091 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 workflow-concepts, differing in 0 lines, and is treated as a copy.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.