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/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/prep"><img src="https://agentmods.dev/badge/skills/mikestankavich/claude-ship-workflow/prep.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.00000 | $0.03811 |
| Opus 5.5 | $0.00000 | $0.01524 |
| Sonnet 5.5 | $0.00000 | $0.00762 |
| Haiku 4.5 | $0.00000 | $0.00381 |
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 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 — 292 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.
- 1mo ago Changed · +16 lines a2f530b0cf0a
- 1mo 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 costs nothing until one of its globs matches a file; then it loads 3,811 tokens. 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
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).
agy-lead
Orchestrate an ongoing task with AGY while the current agent owns key decisions, review, and delivery. Use when the user invokes /agy-lead or asks you to coordinate a task using AGY.
pave-catalog
Build a service catalog — schema, starter entries, and governance model. Produces what information to capture per service, how it's maintained, and where it lives. Use when asked to "service catalog", "what services do we have", "catalog our services", "service inventory", or "who owns what".
atlas-present
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
buzz-community
Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
crest-okr
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".