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 skills/mikestankavich/claude-ship-workflow/batchnpx skills add mikestankavich/claude-ship-workflow --skill batchgit clone --depth 1 https://github.com/mikestankavich/claude-ship-workflowWrote 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/skills/mikestankavich/claude-ship-workflow/batch)<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="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.00031 | $0.04986 |
| Opus 5 | $0.00015 | $0.02493 |
| Sonnet 5 | $0.00006 | $0.00997 |
| Haiku 4.5 | $0.00003 | $0.00499 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 346 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 writtendry-runordry 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.
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.
- 5d ago First seen · 346 lines · 31 tokens per session scan A e5d5cf93274c
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 4,986 once invoked, about $0.0002 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-31.
Other skills, from other repositories
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.
refactoring
Safe, test-backed code restructuring in small steps.
designer
Settle the look before the pixels — audience and context first, then the base and the delta, taste settled by looking at real states, accessibility as the floor, one design language committed to DESIGN.md as tokens with roles. A command the user types, for work with an interface someone will see; standalone, no other…
decision-record
Keep the index of the project's settled decisions in .genius/DECIDED.md — one line per decision, pointing at the fight that settled it, earned by one test: would a future stranger re-fight this? Use when such a decision lands, when a design might contradict a settled one, or when another skill needs the index…
writing-javascript
How browser JavaScript is written in this repo — both surfaces now speak one modern dialect and this says what that means for the code you type, where ES modules are impossible and where they are merely unused, and how to pick a feature (Baseline plus a file:// gate). Covers functional idiom over imperative DOM work…
writing-python
How Python is written in this repo — free functions over classes, structured returns instead of mutated arguments, comprehensions, no module state, and the stdlib-only, annotation-free, Python 3.8 dialect the AST lints enforce. Covers modular structure and the import-layer rule, DRY without copying a helper into a…