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-directiongit 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-direction)<a href="https://agentmods.dev/skills/stefan-stepzero/shipkit/shipkit-direction"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-direction/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-direction"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-direction.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.00080 | $0.01336 |
| Opus 5.5 | $0.00032 | $0.00534 |
| Sonnet 5.5 | $0.00016 | $0.00267 |
| Haiku 4.5 | $0.00008 | $0.00134 |
Grade A, and why
shipkit-direction 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-direction — Define the Foundation
Purpose: The consumer-facing DIRECTION entry point. Takes a project (a repo, a one-line goal, or nothing) and drives the definitional foundation — vision → stage → users → product → engineering → goals — to a coherent bar, autonomously: it proposes everything it can ground in a cited signal and asks only the few high-leverage decisions.
shipkit-direction is a thin caller. It does not implement its own loop — it states the
what (steps + bar + which steps are elicitive) and hands off to the engine
(shipkit-orchestrate), which owns the how (dispatch → reconcile → re-dispatch →
stop-at-bar, with elicitation bubbled to the main session). This replaces the previous
forked direction loop.
Read first: install/shared/references/ground-or-ask-calibration.md (the propose-vs-ask
rule), install/shared/references/elicitation-protocol.md (the marker/resume mechanics the
elicitive steps use), and install/shared/references/core-automation.md (the engine contract).
What it does
Invoke shipkit-orchestrate in autonomous mode (propose variant) over the Direction
steps. The engine runs inline in the main session, dispatches each step, reconciles its
artifact against the bar, bubbles any elicitation marker to the user, and stops when the
foundation is coherent.
Pass the engine the four inputs (calling interface in shipkit-orchestrate/SKILL.md):
| Input | For Direction |
|---|---|
| steps | the definitional chain, in order: why-project → stage → product-discovery → product-definition → engineering-definition → product-goals → engineering-goals, with review-direction as the assess gate |
| bar | each step's named .shipkit/ artifact exists AND is grounded (every field cited or flagged per the calibration), AND review-direction passes (coherent, no gaps) |
| mode | autonomous — propose the grounded foundation, ask only the high-leverage few (fall back to interactive when signals are thin) |
| elicitive | the steps that may pause for input: why-project, stage, product-discovery, product-goals, engineering-goals (plus feedback-bug on the feedback re-entry path — six in all). The product-definition / engineering-definition synthesis steps are not elicitive — they derive from upstream artifacts and only propose. Each elicitive step emits NEEDS_ELICITATION:<slug>; the engine batches the questions to the user and resumes. |
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 · 110 lines · 80 tokens per session scan A 52f5a0c366fe
shipkit-direction is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 1,336 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.