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 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/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.
<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>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.05493 |
| Opus 5.5 | $0.00012 | $0.02197 |
| Sonnet 5.5 | $0.00006 | $0.01099 |
| Haiku 4.5 | $0.00003 | $0.00549 |
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.
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 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.
- 1mo ago Changed · +29 lines 0d4dd5ff430f
- 1mo 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 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.
Other skills, from other repositories
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
g-update
Fix G-Forge-managed files via Step 0 staleness preflight (stops with zero writes if cache lags GitHub, directs to /plugins first), then realigns CLAUDE.md Rules, agents, architecture rules, hooks, and native pre-commit gate. Safe — G-Forge markers only.
debrief
Review what agents accomplished, surface loose ends across sessions.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.