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/stefan-stepzero/shipkit/shipkit-shipnpx skills add stefan-stepzero/shipkit --skill shipkit-shipgit clone --depth 1 https://github.com/stefan-stepzero/shipkitWhat 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 | $0.00063 | $0.01127 |
| Opus 5 | $0.00032 | $0.00563 |
| Sonnet 5 | $0.00013 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
shipkit-ship 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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-ship — Build to Done
Purpose: The consumer-facing BUILD entry point. Takes a plan
(.shipkit/plans/) and drives it to a confirmed, ground-truth completion bar.
shipkit-ship is a thin caller. It does not implement its own build loop — it states the what (steps + bar) and hands off to the engine, which owns the how (partition → fan-out → reconcile → integrate → stop-at-bar). This is Shipkit-native drive-to-done: one engine, one completion contract.
Read first: install/shared/references/core-automation.md — the contract the engine
runs. This skill only assembles the call.
What it does
Invoke shipkit-orchestrate in autonomous mode over the plan. Nothing more —
the engine runs inline in the main session, launches the parallel build, reconciles
against ground truth, integrates serially, and stops at the bar.
Pass the engine the four inputs (calling interface in
install/skills/shipkit-orchestrate/SKILL.md):
| Input | For a build |
|---|---|
| steps | the plan's phases / file-ownership clusters, in dependency order — the units to build (from .shipkit/plans/<feature>.json) |
| bar | the ground-truth completion criteria (below) — stated explicitly; the engine advances only when they are true on disk / in git |
| mode | autonomous (build runs unattended to the bar) — add the scale toggle for very large / long builds |
| elicitive | normally none — a build should run with the spec/plan already resolved. If a step genuinely needs a human decision, mark it elicitive so the engine bubbles it (never inside a workflow), rather than letting a worker guess. |
The bar (state it — don't let a worker self-report "done")
A build is done only when all of these are reconciled (verified, not reported):
- Functional surface complete — every element the no-gaps spec named across the four dimensions (applications / datastores / contracts / integrations) is built, not just the happy path. A frontend that implies a backend has the backend.
- Plan acceptance met — every acceptance criterion / phase gate in the plan passes.
- Tests green — the plan's named checks (tests, build, lint) pass.
- Integrated — work is committed, rebased onto the target branch, and landed per the integration policy (serial, one lane at a time, never forced past unverified work).
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.
- yesterday First seen · 103 lines · 63 tokens per session scan A 44498f2acc92
shipkit-ship is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,127 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.