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/awarenessnpx skills add maxtechera/ship --skill awarenessgit 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.00040 | $0.01768 |
| Opus 5 | $0.00020 | $0.00884 |
| Sonnet 5 | $0.00008 | $0.00354 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
ship-awareness-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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Awareness Supervisor
Own Awareness deliverables during Stage 5 (Parallel Execution).
Product Type Branch
Read intake.product_type before producing any deliverables.
oss_tool→ run OSS Demo-First Mode instead of standard awareness packsaas|course|service→ run standard awareness deliverables 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)
OSS Demo-First Mode (when intake.product_type: oss_tool)
Core principle: Demo-first > readme-first. Nobody reads docs and decides to buy. They try it, get impressed, and convert. The free content IS the sales page.
OSS Awareness Inputs (Required)
intake.product_brief(includes GitHub repo, install command, friction point)validate.oss_pain_quotes(10+ real quotes)validate.friction_point(where course CTA fires)validate.search_intent_map(5-10 keywords)
OSS Awareness Deliverables (Required)
- Reel scripts — Problem (15-30s): show the pain moment, no solution yet. CTA: GitHub repo URL.
- Reel scripts — Fix (30-45s): show the install + the moment it works. CTA: link in bio → free install.
- Reel scripts — Architecture (45-60s): show how it works under the hood. CTA: course link.
- Long-format script (10-20min YouTube): full demo end-to-end — install, real use case, result. CTA: GitHub + newsletter + course.
- Newsletter issue draft: written breakdown of the architecture for NODO subscribers.
- GitHub README CTA copy: 2-3 lines added to README pointing to course at the friction point.
- Hook library: 5-10 hooks per reel format (problem/fix/architecture) sourced from
validate.oss_pain_quotes.
OSS Reel Template
Each tool gets 3 reels following this structure:
Reel 1 — The Problem (15-30s)
Hook: [verbatim pain quote or common frustration]
Show: the failure moment (agent forgets / says done but it's wrong / launch pipeline breaks)
End: "There's a fix." + GitHub URL on screen
CTA: "[tool name] — free on GitHub"
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 · 168 lines · 0 tokens per session scan A 36caf03d598a
ship-awareness-supervisor is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,768 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.