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/enginenpx skills add maxtechera/ship --skill enginegit 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.00019 | $0.00569 |
| Opus 5 | $0.00010 | $0.00284 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
content-engine 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Engine
Content planning and production queue management. Manages the full lifecycle: ideation → scheduling → scripting → posting → measurement.
Core Functions
1. Queue Management
Maintain a prioritized list of content ideas:
id, topic, format, platform, priority, status, scheduled_date, published_url
Statuses: idea → scripted → recorded → edited → scheduled → published → measured
2. Idea Intake
When a new idea arrives:
- Classify: format (reel / carousel / thread / blog), platform, priority (1-4)
- Deduplicate: check if similar idea is already in queue
- If it fits an active ship-engine run: tag it with the run ID and stage
3. Research → Content Pipeline
For each approved idea:
- Pull relevant research evidence (VoC, data, sources)
- Delegate to
content-composefor pillar draft - Delegate to
content-waterfallfor platform derivatives - Auto-schedule derivatives (drafts only — no auto-publish)
4. Intake Preflight
Before creating content artifacts for a ship-engine run, require:
intake.product_briefpresentintake.interviewpresentintake.research_kickoffpresent
If any are missing: block content creation, log missing items, request from run owner.
5. Calendar State
Track what's scheduled vs what's published:
scheduled_this_week: [list of scheduled items with dates/times]
published_this_month: [list with permalinks + initial metrics]
6. Analytics Sync
When live permalinks exist:
- Trigger
content-measurefor day-1 and week-1 snapshots - Store results in queue item record
- Pass feedback events to
content-feedback-loop
Guardrails
- Draft autoscheduling is allowed; auto-publishing to social accounts is not
- Never fabricate research evidence or metrics
- Never mark content
verifiedorlivewithout a live permalink - Respect locked/confirmed items in the schedule — only reschedule drafts
Outputs
- Updated content queue with statuses and scheduled dates
- Artifact links per item (pillar draft, waterfall bundle, published URL)
- Calendar view for the current week
- Measurement summary when snapshots exist
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 81 lines · 0 tokens per session scan A 4757ac12d11e
content-engine is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 569 once invoked, about $0.0001 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…