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/maxtechera/ship/launchnpx skills add maxtechera/ship --skill launchgit clone --depth 1 https://github.com/maxtechera/shipWhat 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.00037 | $0.01096 |
| Opus 5 | $0.00018 | $0.00548 |
| Sonnet 5 | $0.00007 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
ship-launch-supervisor 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Launch Supervisor
Own Stage 6 (Pre-Launch approval gate) and Stage 7 (LAUNCH).
Shared Contracts (DRY)
Follow canonical contracts in openclaw-config/skills/engine/WORKFLOW.md:
Gate Prefill Requirement (owner-facing)Writeback Schema (Canonical)Deliverable Lifecycle States (Stage 9)
Inputs (Required)
- Parallel workstream artifacts:
awareness.*lead_capture.*nurture.*closing.*
- Linear Stage 6 + Stage 7 tickets
Credential Preflight (Required Before Deploy)
Before any Stage 7 deploy action (publishing to live URLs, submitting to directories, scheduling social posts):
- Run:
python3 credentials/scripts/check_local.py --json - Exit 0 → proceed.
- Exit 1 → halt. Print
fix_cmdfor each failure. Post to Linear ticket with exact missing credentials. Do not deploy.
Intentionally redundant with the engine-level gate — the launch supervisor must never skip this check, even when invoked directly. Full credential registry: credentials/SKILL.md
Deliverables (Required)
- Pre-launch readiness checklist linked (one line per workstream with artifact links)
- owner approval request posted with explicit decision options
- Launch-day playbook linked
- Directory submission list + statuses linked
- Scheduled/publish-ready content pack linked
- Final social push package linked with explicit owner decision request (
Approve Push/Revise Package/Hold Push)
Verification
- All referenced artifacts resolve (no missing links)
- Launch CTAs route to capture mechanisms (UTMs + forms)
- In
production, launch artifacts are critic-verified (PASS) before markingverified/live - Stage 6 and Final Social Push requests are posted as prefilled Decision Packets
- No broad social publishing happens before final social push package approval
Quality Gate (PASS/REVISE)
- PASS: readiness checklist is complete, critic-verified in
production, and approval decisions are recorded via prefilled Decision Packets - REVISE: missing artifacts, broken links, capture path not wired, or critic verdict
REVISE
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 · 99 lines · 37 tokens per session scan A e8b449dd04f8
ship-launch-supervisor is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,096 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…