dsh-playbook

dsh-playbook is a command for Claude Code from ZSeven-W/dsh-crew. It costs 24 tokens per session (1,092 once invoked), scanned A, a copy of playbook, MIT.

A guide for assigning work to DSH workers, including choosing a worker level, writing a complete brief, using parallel work, and checking results.

In plain words
What is it for?
Use it when delegating coding, configuration, debugging, or design tasks through the DSH worker tools.
Why use it?
It helps match simple tasks to quick workers and complex debugging or design work to workers suited to deeper reasoning, with practical safety checks.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dsh-crew plugin — 3 skills, 8 commands, 2 agents, 1 MCP server shipped together

Good fit Use it when delegating coding, configuration, debugging, or design tasks through the DSH worker tools.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/zseven-w/dsh-crew/dsh-playbook
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ZSeven-W/dsh-crew

Made for: Claude Code.

Or install dsh-crew, the plugin that ships this one along with the rest of its 3 skills, 8 commands, 2 agents, 1 MCP server.

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 dsh-playbook

README.md
[![agentmods](https://agentmods.dev/badge/commands/zseven-w/dsh-crew/dsh-playbook/github.svg)](https://agentmods.dev/commands/zseven-w/dsh-crew/dsh-playbook)
Your own site
<a href="https://agentmods.dev/commands/zseven-w/dsh-crew/dsh-playbook"><img src="https://agentmods.dev/badge/commands/zseven-w/dsh-crew/dsh-playbook/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.

agentmods 80×15 button for dsh-playbook

Your own site · 80×15
<a href="https://agentmods.dev/commands/zseven-w/dsh-crew/dsh-playbook"><img src="https://agentmods.dev/badge/commands/zseven-w/dsh-crew/dsh-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 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,092 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 95% copy Near-identical to another mod 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.00024 $0.01092
Opus 5 $0.00012 $0.00546
Sonnet 5 $0.00005 $0.00218
Haiku 4.5 $0.00002 $0.00109

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

Security

Grade A, and why

dsh-playbook 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 10d 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

This is a copy

95% identical to playbook — 2 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.

grok/commands/dsh-playbook.md · 67 lines

How it starts

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

When the user asks how to dispatch work to DSH workers — tier choice, writing a brief, parallelism, verifying results, guardrails — answer from the playbook below. Point to the relevant section rather than reciting it whole.

In this host the dsh-crew MCP tools are namespaced: wherever the playbook says dsh_run_worker, call dsh-crew__dsh_run_worker, and likewise for the other five tools.

DSH Crew — Dispatch Playbook

How to delegate work to DSH workers well. The tool descriptions carry the mechanics; this playbook is the decision layer.

1. Choosing a worker

flash — mechanical, well-scoped work:

  • Rename a symbol in one or two files and update the obvious call sites.
  • Read a config file and report the values of a few keys.
  • Add a unit test for an existing function, following the file's existing style.

pro — multi-file work, debugging, design judgment:

  • Refactor a module that is used across the repo and update every caller.
  • Diagnose a flaky test or a race condition by reading logs and tracing the code.
  • Design a new API or file layout with tradeoffs to weigh, then implement it.

When in doubt, start with flash: escalate_on_failure retries a failed blocking flash run once on pro, so evidence, not guesswork, decides.

worker="agy" / worker="grok" is explicit opt-in. Set it only when the user explicitly asks for that CLI, never as a default. Two caveats to tell the user: grok refuses to start repo-local MCP servers in untrusted folders (global installs are unaffected; change directory or pass --trust), and agy runs with full approval because it has no workspace-scoped permission mode.

2. Writing the brief

The worker has zero conversation context. Every task string must be self-contained:

  • Absolute paths for every file and directory involved.
  • Exact acceptance criteria: what must be true when done, and how to verify it.
  • What NOT to touch (generated files, unrelated modules, lockfiles).
  • Never commit, push, or publish unless the user explicitly authorized it — write that into the brief.

Read the full file on GitHub · 67 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. 10d ago First seen · 67 lines · 24 tokens per session scan A ea56eb8e09d8

Subscribe to this mod's changes

dsh-playbook is a command published in the GitHub repository ZSeven-W/dsh-crew (136 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 1,092 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to playbook, differing in 2 lines, and is treated as a copy.