claude-code-best-practice: Command for Claude Code

.claude/commands/workflows/best-practice/workflow-claude-subagents.md

workflow-claude-subagents is a command for Claude Code from shanraisshan/claude-code-best-practice. It costs 12 tokens per session (1,587 once invoked), scanned A, original, MIT.

A reporting workflow that checks whether Claude Code's subagent documentation has changed across recent versions.

In plain words
What is it for?
It helps compare official documentation and changelogs with the local subagents report, then present any added or removed fields and subagents.
Why use it?
It helps reveal when documented settings or built-in subagents no longer match the local reference report before anyone updates it.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; mentions Claude Code.

This is shanraisshan/claude-code-best-practice's own configuration. It tells Claude Code how to work on claude-code-best-practice itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-best-practice configures →

About the project

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.

shanraisshan/claude-code-best-practice · 65,734 stars · on GitHub · linkedin.com

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/shanraisshan/claude-code-best-practice/main/.claude/commands/workflows/best-practice/workflow-claude-subagents.md
Clone the repo
git clone --depth 1 https://github.com/shanraisshan/claude-code-best-practice

Made for: Claude Code.

Wrote 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.

agentmods badge for workflow-claude-subagents

README.md
[![agentmods](https://agentmods.dev/badge/commands/shanraisshan/claude-code-best-practice/workflow-claude-subagents.svg)](https://agentmods.dev/commands/shanraisshan/claude-code-best-practice/workflow-claude-subagents)
Your own site
<a href="https://agentmods.dev/commands/shanraisshan/claude-code-best-practice/workflow-claude-subagents"><img src="https://agentmods.dev/badge/commands/shanraisshan/claude-code-best-practice/workflow-claude-subagents.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,587 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01587
Opus 5 $0.00006 $0.00794
Sonnet 5 $0.00002 $0.00317
Haiku 4.5 $0.00001 $0.00159

Measured 9d ago against content hash 3bd0c2caed09, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

workflow-claude-subagents 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/workflows/best-practice/workflow-claude-subagents.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow Changelog — Subagents Report

You are a coordinator for the claude-code-best-practice project. Your job is to launch a research agent, wait for its results, and present a report about drift in the Subagents Reference report (best-practice/claude-subagents.md).

This workflow checks for exactly two types of drift:

  1. Frontmatter fields — any field added or removed in the official docs
  2. Official sub-agents — any built-in agent added or removed

Versions to check: $ARGUMENTS (default: 10 if empty or not a number)

This is a read-then-report workflow. Launch the agent, merge findings, and produce a report. Only take action if the user approves.


Phase 1: Launch Research Agent

Spawn the workflow-claude-subagents-agent with this prompt:

Research the claude-code-best-practice project for subagents report drift. Check the last $ARGUMENTS versions (default: 10).

Fetch these 2 external sources:

  1. Sub-agents Reference: https://code.claude.com/docs/en/sub-agents
  2. Changelog: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

Then read the local report (best-practice/claude-subagents.md).

Check for exactly two things:

  1. Frontmatter fields: Compare the official docs' supported frontmatter fields table against the report's Frontmatter Fields table. Flag any fields that were added or removed.
  2. Official sub-agents: Compare the official docs' built-in subagents list against the report's official agents table. Flag any agents that were added or removed.

Phase 2: Read Previous Changelog Entries

While the agent is running, read changelog/best-practice/claude-subagents/changelog.md to get the last 25 entries. Parse the priority actions to identify:

  • Recurring items — issues that appeared before and are still unresolved
  • New items — issues appearing for the first time
  • Resolved items — previously flagged issues now fixed

Phase 3: Generate Report

Read the full file on GitHub · 137 lines

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.

  1. 9d ago First seen · 137 lines · 12 tokens per session scan A 3bd0c2caed09

Subscribe to this mod's changes

workflow-claude-subagents is a command published in the GitHub repository shanraisshan/claude-code-best-practice (65,734 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,587 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.