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/nurturenpx skills add maxtechera/ship --skill nurturegit 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.00036 | $0.00983 |
| Opus 5 | $0.00018 | $0.00491 |
| Sonnet 5 | $0.00007 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
ship-nurture-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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Nurture Supervisor
Own Nurture deliverables during Stage 5 (Parallel Execution).
Product Type Branch
Read intake.product_type from blackboard before executing.
oss_tool→ OSS Nurture Modesaas | course | service→ standard nurture deliverables below
OSS Nurture Mode
For OSS tools, there is no paid email sequence — the product is free. Nurture is the content drip from GitHub install → newsletter → course purchase.
Deliverables:
- 3-email welcome sequence linked (day 0: welcome + tool intro; day 3: architecture deep-dive; day 7: course CTA)
- MailerLite automation config linked — sequence fires when subscriber tagged
{tool-name}-install(set by lead-capture stage) - Content drip schedule linked — long-format YouTube or newsletter issue linked in email 2
- Test email evidence linked (rendering + links + unsubscribe)
Writeback keys: nurture.oss_welcome_sequence, nurture.oss_drip_schedule
Quality Gate (OSS):
- PASS: 3-email sequence exists, test evidence linked, MailerLite tag trigger configured, drip schedule ready, critic PASS in
production - REVISE: missing test evidence, broken CTA links, tag trigger not configured, or critic REVISE
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)
strategy.ship_planvalidate.icp(VoC + objections)lead_capture.offer_stackandlead_capture.capture_wiring- Linear Nurture ticket
Deliverables (Required)
- Email welcome/nurture sequence (copy + timing) linked
- Automation import plan or evidence of live import linked
- Test email evidence (rendering + links + unsubscribe) linked
- Content drip schedule (14-day) linked
Verification
- Test email received and passes basic rendering checks
- CTAs align with offer and funnel stage
- Copy is humanized (no generic AI cadence)
- In
production, each deliverable is critic-verified (PASS) before moving toverified/live
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.
- 3d ago First seen · 90 lines · 36 tokens per session scan A a9fc54c9edd3
ship-nurture-supervisor is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 983 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…