batch

batch is a skill for Claude Code from mikestankavich/claude-ship-workflow. It costs 31 tokens per session (5,493 once invoked), scanned A, original, MIT.

A batch workflow that selects Todo tickets and gives each one its own Git worktree (isolated working folder) and pull request for review.

In plain words
What is it for?
Use it to dispatch a capped group of prepared tickets, optionally preview the selection with a dry run, and create one pull request per ticket.
Why use it?
It organizes overnight ticket work while respecting blocking dependencies and leaves a summary for the morning.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions subagents.

Part of the csw plugin — 5 skills shipped together

Good fit Use it to dispatch a capped group of prepared tickets, optionally preview the selection with a dry run, and create one pull request per ticket.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mikestankavich/claude-ship-workflow/batch
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.

Any agent
npx skills add mikestankavich/claude-ship-workflow --skill batch
Clone the repo
git clone --depth 1 https://github.com/mikestankavich/claude-ship-workflow

Made for: Claude Code.

Or install csw, the plugin that ships this one along with the rest of its 5 skills.

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 batch

README.md
[![agentmods](https://agentmods.dev/badge/skills/mikestankavich/claude-ship-workflow/batch/github.svg)](https://agentmods.dev/skills/mikestankavich/claude-ship-workflow/batch)
Your own site
<a href="https://agentmods.dev/skills/mikestankavich/claude-ship-workflow/batch"><img src="https://agentmods.dev/badge/skills/mikestankavich/claude-ship-workflow/batch/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 batch

Your own site · 80×15
<a href="https://agentmods.dev/skills/mikestankavich/claude-ship-workflow/batch"><img src="https://agentmods.dev/badge/skills/mikestankavich/claude-ship-workflow/batch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,493 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.00031 $0.05493
Opus 5.5 $0.00012 $0.02197
Sonnet 5.5 $0.00006 $0.01099
Haiku 4.5 $0.00003 $0.00549

Measured 1mo ago against content hash 0d4dd5ff430f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

skills/batch/SKILL.md · 375 lines

How it starts

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

Dispatch a batch of tickets

Announce at start: "Using csw:batch to dispatch tonight's tickets."

Tonight's invocation carried: $ARGUMENTS

Two modifiers, and they compose:

  • A bare integer lowers tonight's cap. Never raises it — see Step 2.
  • --dry-run, also written dry-run or dry run, runs selection and stops — see Step 3.

So /csw:batch 2 --dry-run shows tonight's plan cut at 2 without dispatching anything. Anything else in $ARGUMENTS is not a modifier: say what you ignored and why, rather than guessing at what it meant.

Before the first run: the prerequisite

This loop's first filter is "drop blocked tickets," and it only works if the tracker knows what blocks what. If blockedBy is empty on most tickets while relatedTo carries three or four links each, the dependency information exists but is in the wrong field and in prose.

Backfill blocking relations on the Todo column before relying on this. Check a sample first, and if blockedBy is empty across the board, say so and stop rather than dispatching a batch whose ordering constraints are invisible.

Prepped tickets dispatch better. /csw:prep <ticket> leaves a spec and its open questions on the ticket, and csw:work Step 2 reads them, so a question that would have cost a whole dispatch to discover is already answered when the loop reaches it. It is not required, and this loop does not skip unprepped tickets — an optional command that silently became a gate would be a new manual step in front of every ticket in the column.

Step 1: Pull the candidates

Either way, this step ends with candidates_json holding a JSON array in the shape Step 2 pipes into csw-batch-filter:

[
  {
    "id": "ENG-1075",
    "state": "Todo",
    "priority": 2,
    "labels": ["migration"],
    "blockedBy": [],
    "relatedTo": ["ENG-1080", "ENG-1081"]
  }
]

Which way depends on one key:

csw-config get trackerCommand

Empty — read the tracker. Read every Todo ticket from the tracker named by csw-config get tracker and shape it into the array above yourself. This is the default, and it is what tracker: linear does through MCP.

Read the full file on GitHub · 375 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. 1mo ago Changed · +29 lines 0d4dd5ff430f
  2. 1mo ago First seen · 346 lines · 31 tokens per session scan A e5d5cf93274c

Subscribe to this mod's changes

batch is a skill published in the GitHub repository mikestankavich/claude-ship-workflow (3 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 5,493 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-31.