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-preflightgit 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-preflight)<a href="https://agentmods.dev/skills/stefan-stepzero/shipkit/shipkit-preflight"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-preflight/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-preflight"><img src="https://agentmods.dev/badge/skills/stefan-stepzero/shipkit/shipkit-preflight.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.00029 | $0.06218 |
| Opus 5.5 | $0.00012 | $0.02487 |
| Sonnet 5.5 | $0.00006 | $0.01244 |
| Haiku 4.5 | $0.00003 | $0.00622 |
Grade B, and why
shipkit-preflight scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Build passes without warnings How it starts
The opening of the file, as written. The whole thing — 697 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-preflight - MVP Production Readiness Audit
Purpose: Ensure your project is ready for first users — the essentials that can't wait.
What it does: Runs an MVP-focused production checklist covering security, data integrity, error handling, UX basics, and legal compliance. Generates .shipkit/preflight.json with structured results. For scale/enterprise readiness (observability, performance, operational maturity), use /shipkit-scale-ready after you have traction.
Output format: JSON — readable by Claude, machine-readable by other tools, and the single source of truth for production readiness status.
Philosophy: With AI dev, building is cheap — but security, data integrity, and user trust aren't. This checklist keeps what matters for MVP while deferring optimization concerns.
When to Invoke
User triggers:
- "Am I ready to ship?"
- "Production readiness check"
- "Preflight", "Go live check"
- "Is this ready for users?"
- "Launch checklist"
For thorough mode (deep code review per partition):
- "Thorough preflight", "Deep preflight"
- "Really scrutinize before launch"
- → See Thorough Mode section
Workflow position:
- After features are implemented
- Before deploying to production
- When transitioning from "it works" to "it's shippable"
Prerequisites
This skill aggregates context from other skills. It will route you to create missing context.
| Needed Context | Source Skill | File | Required? |
|---|---|---|---|
| Tech stack, deployment target | /shipkit-project-context |
stack.json |
Yes |
| Vision, constraints, scale | /shipkit-why-project |
why.json |
Yes |
| Architecture decisions, auth model | /shipkit-engineering-definition |
architecture.json |
Recommended |
| Data shapes, what's stored | /shipkit-engineering-definition |
engineering-definition.json |
Recommended |
| Feature specs | /shipkit-spec |
specs/active/*.json |
Helpful |
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/checklists/auth-checks.md 5.2 KB
- references/checklists/data-privacy-checks.md 5.7 KB
- references/checklists/database-checks.md 5.0 KB
- references/checklists/deployment-checks.md 6.6 KB
- references/checklists/payment-checks.md 4.9 KB
- references/checklists/universal-checks.md 16 KB
- references/example.json 15 KB
- references/output-schema.md 9.1 KB
- references/README.md 1.3 KB
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 · 697 lines · 29 tokens per session scan B 1cf0a2232877
shipkit-preflight is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 6,218 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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.