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 stefan-stepzero/shipkit --skill shipkit-shipgit clone --depth 1 https://github.com/stefan-stepzero/shipkitWrote 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/stefan-stepzero/shipkit/shipkit-ship)<a href="https://agentmods.dev/skills/stefan-stepzero/shipkit/shipkit-ship"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-ship/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/stefan-stepzero/shipkit/shipkit-ship"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-ship.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.00063 | $0.01127 |
| Opus 5.5 | $0.00025 | $0.00451 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,127 once invoked, about $0.0003 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
anti-deception
Use before responding to pressure for agreement, manufactured urgency, authority appeals, or requests to certify unsupported claims; separate evidence from persuasion and state uncertainty.
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
wrap-up
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/ /log.md or career-vault/log.md, one entry per project touched, never to new-client. Use when the student…
pick-up
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
grill-me
One move you can run on anything: point grill-me at a target and it makes you defend your thinking from first principles until the true matter is clear. Point it at your working contract and it rewrites the weak lines in place. Point it at a brief and it produces a Requirements Handshake. Point it at research, an…
information-architecture
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or UI.