What is ship-closing-supervisor?

A closing-workstream guide for preparing pricing, checkout, objection-handling, and post-purchase materials. For free open-source tools, it treats closing as selling a related course rather than the tool itself.

Use it to create or link a sales page, set the offer price, answer common objections, prepare confirmation and access messages, and verify checkout.

It organizes the final steps needed to turn interest into a purchase and checks that the payment flow and follow-up materials are ready.

ship-closing-supervisor — Skill by maxtechera

Install

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.

agentmods

npx agentmods add skills/maxtechera/ship/closing

Any agent

npx skills add maxtechera/ship --skill closing

Clone the repo

git clone --depth 1 https://github.com/maxtechera/ship

Made for: Claude Code, Codex.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,001 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00036	$0.01001
Opus 5	$0.00018	$0.00500
Sonnet 5	$0.00007	$0.00200
Haiku 4.5	$0.00004	$0.00100

Measured 2d ago against content hash c0b369b7e66a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ship-closing-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.

supervisors/closing/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship Closing Supervisor

Own Closing deliverables during Stage 5 (Parallel Execution).

Product Type Branch

Read intake.product_type from blackboard before executing.

oss_tool → OSS Closing Mode
saas | course | service → standard closing deliverables below

OSS Closing Mode

For OSS tools, "closing" means course conversion — not SaaS checkout. The product is free; the course is the paid offer.

Deliverables:

Course sales page linked (path: /tools/{slug}/course, sourced from intake.course_upsell_url or built fresh)
Pricing: one price, no free tier, no trial. Scarcity is the friction point from intake.friction_point.
Objection pack linked — 5 objections sourced from validate.oss_pain_quotes (why not just read the docs? why pay when the tool is free? etc.)
Post-purchase sequence linked: confirmation email + course access link + GitHub stars ask
Checkout verification evidence linked (test flow)

Writeback keys: closing.oss_course_page, closing.oss_objections, closing.oss_post_purchase

Quality Gate (OSS):

PASS: course page exists, objection pack uses ICP language, post-purchase sequence is ready, checkout tested, critic PASS in production
REVISE: missing test flow, objections don't match ICP language, no course page URL, 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_plan (pricing hypothesis + guarantee)
validate.icp (objections)
Linear Closing ticket

Deliverables (Required)

Pricing page / checkout flow artifact linked (or deployment URL)
Objection handling pack linked (FAQ + email responses + deck bullets)
Post-purchase email sequence outline linked
Checkout verification evidence linked (test flow)

Verification

Checkout flow tested end-to-end (evidence logged)
Objection pack uses ICP language and matches offer
Pricing/guarantee terms consistent across assets
In production, each deliverable is critic-verified (PASS) before moving to verified/live

Read the full file on GitHub · 91 lines

Changes

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 · 91 lines · 36 tokens per session scan A c0b369b7e66a

Subscribe to this mod's changes

ship-closing-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 1,001 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.

E-commerce Learning and teaching Planning

b2c-onboarding

Get started with Salesforce B2C Commerce development. Use this skill when the user is new to B2C Commerce, wants to set up a fresh development environment, is asking "how do I get started", needs to install the B2C CLI for the first time, wants to connect a sandbox, or wants to deploy their first cartridge. Triggers…

SalesforceCommerceCloud/b2c-developer-tooling · 153 tokens

tutorial

Interactive 5-minute walkthrough of the Carta CRM plugin. Covers plugin overview, setup verification, how to kick off each skill, and a demo walkthrough of 4 realistic CRM scenarios. Trigger phrases: "carta crm tutorial", "show me the crm tutorial", "how do I use carta crm", "walk me through carta crm", "getting…

carta/plugins · 146 tokens

shopify-partner-marketing

Marketing playbook for Shopify Partners — how an agency or freelancer markets and sells their Shopify services. Captures the Shopify Academy course 'Marketing Your Shopify Services as a Partner' plus public Partner Program guidance. Use whenever a Shopify Partner (agency, freelancer, dev, consultant) wants to position…

MSApps-Mobile/claude-plugins · 236 tokens

knowledge-map

Guide-and-script skill for building course knowledge maps. Use it to turn a course topic, syllabus, textbook outline, notes, or teaching materials into a structured framework, key concept explanations, concept dependencies, and optional Markdown / Markmap / Mermaid / OPML / HTML outputs.

Orkas-AI/Orkas-Awesome-AgentSkills · 2 tokens

retrieval-practice

Guide-type skill for generating retrieval practice materials that make learners reconstruct knowledge from memory. Use it to create teacher-facing or facilitator-facing active-recall questions, low-stakes quizzes, answer notes, misconception checks, and short implementation scripts.

Orkas-AI/Orkas-Awesome-AgentSkills · 4 tokens

socratic-tutor

Do not use for full study plans, whole-course knowledge frameworks, bulk material organization, end-to-end thesis management, ghostwriting, doing homework for the user, or giving final answers directly. If the user asks for an adjacent but overly broad learning task, do not introduce other skills and do not reject…