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/strategynpx skills add maxtechera/ship --skill strategygit 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.00031 | $0.01078 |
| Opus 5 | $0.00015 | $0.00539 |
| Sonnet 5 | $0.00006 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
ship-strategy-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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Strategy Supervisor
Own Stage 4 (STRATEGY). Produce the Ship Plan that the 4 parallel workstreams execute.
Product Type Branch
Read intake.product_type from blackboard before producing the Ship Plan.
oss_tool: The Ship Plan must define the OSS conversion chain:
GitHub install → newsletter signup → nurture → course purchase.
- Channel priorities: GitHub README CTA + reel content first. Paid lane is optional for v1 (organic-first default).
- Offer section: replace SaaS pricing with course pricing only. No free tier, no trial.
- Distribution: community-driven (GitHub, dev newsletters, Twitter/X, HN Show). Ads are secondary.
saas | course | service: Standard Ship Plan structure below.
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)
validate.validation_reportvalidate.icp- Linear Stage 4 ticket
Deliverables (Required)
- Ship Plan doc linked in Linear
- Parallel workstream tickets created/updated with Inputs/Deliverables/Verification/Artifacts
- Budget + spend policy recorded
- Strategy Lock Pack posted as a prefilled Decision Packet for human approval (to prevent premature fanout)
- Persona Callout Pack linked (library + Meta playbook + Meta pack)
- Blackboard key
strategy.ship_planwritten
Ship Plan (minimum sections)
- Positioning: one-liner, value prop, differentiation
- Offer + pricing hypothesis
- Channel priorities (primary/secondary)
- Content strategy mapped to pain themes (VoC-driven)
- Distribution plan (who/where/how often)
- Persona callout strategy: avatar band (3-12 default), hook families, proof stack, CTA families
- Paid lane split:
paid.prospectingvspaid.retargetingmapped to shared hook IDs - Success targets (visitor -> lead -> activation -> revenue)
- Dependencies for parallel workstreams
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.
- 2d ago First seen · 100 lines · 31 tokens per session scan A eeda78ba2d3e
ship-strategy-supervisor is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,078 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…