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 prepgit 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/prep)<a href="https://agentmods.dev/skills/mikestankavich/claude-ship-workflow/prep"><img src="https://agentmods.dev/badge/skills/mikestankavich/claude-ship-workflow/prep.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.00068 | $0.03610 |
| Opus 5 | $0.00034 | $0.01805 |
| Sonnet 5 | $0.00014 | $0.00722 |
| Haiku 4.5 | $0.00007 | $0.00361 |
Grade A, and why
prep 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 7d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prep a ticket for dispatch
Announce at start: "Using csw:prep to spec without touching the repo."
Invocation: $ARGUMENTS
A batch loop only compounds after a failure: a ticket blocks, the question lands on the ticket, and the next dispatch starts from a better brief — so one wasted dispatch is the price of every question discovered. Prep moves that discovery in front of the dispatch, where it costs a comment instead of a night.
Prep does not implement anything. It reads, it decides everything it can defend a recommendation for, it asks about the little that survives that test, and it writes one comment carrying all of it.
Prep is an interactive command, and that is the design centre rather than a variant of it. The person who can answer typed the invocation and is sitting there for the whole run, so a run ends in one of two states, both of which leave the ticket dispatchable:
- Every question that would block an autonomous build has an answer, recorded on the ticket in the run that asked it.
- There were none, and prep says so.
The second is the common one and the one to aim for. A question left in a comment for someone to notice tomorrow is not a third state — it is the first state, deferred by a day, and that day is exactly what prep exists to remove.
Step 0: Read the config
csw-config json
csw-config path
If csw-config path prints nothing, this repo has no .claude/csw.json. Say so and show the
defaults you are about to use. Prep runs nothing destructive, so this is a note rather than a
stop — but tracker is the one key it genuinely needs, because it decides where the comment
goes.
Step 1: Resolve the ticket
csw-ticket normalize "<the reference from the invocation>"
If the invocation carried no reference, ask which ticket. Do not pick one.
If normalisation exits non-zero, report its message and stop. Prepping the wrong ticket is worse than prepping none: the comment lands somewhere a later dispatch will read it as its brief.
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.
- 7d ago First seen · 276 lines · 0 tokens per session scan A 851fe34972b5
prep is a skill published in the GitHub repository mikestankavich/claude-ship-workflow (3 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 3,610 once invoked, about $0.0003 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
daily-working
End-to-end pipeline: pull a task from Redmine by ID, sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension (claude-in-chrome), and keep the Redmine ticket in sync throughout (in-progress…
issue
Write or rewrite a GitHub issue as a context-rich prompt for another agent. Proves the problem with evidence from the code, gives hints instead of a plan, ends with observable acceptance criteria. Use when the user asks to file, write, draft, open, or rewrite an issue.
startup-lifecycle
End-to-end founder playbook, product-market fit (PMF) telemetry, SaaS monetization, churn analysis, growth loops, and investor-ready unit economics (CAC, LTV, MRR).
requirements
This skill should be used when the user asks to "write requirements", "create user stories", "define acceptance criteria", "decompose a feature", "analyze an issue", "write a PRD", "create user stories", "acceptance criteria", "roadmap", "feature spec", or discusses "INVEST" criteria, "ambiguity", or "story…
fleet
The single-pane session roster (/foundry:fleet) — every active Claude Code session joined to its foundry work-context (epic/atom/governance), over the NATIVE session list. Read-only/advisory. Trigger to see all your parallel sessions at a glance with their foundry context, or when supervising many sessions and asking…
beads-schema
Beads (bd CLI) reference — issue types, statuses, priorities, dependencies, and common commands.