ship

A workflow that carries out an approved coding plan by sending each step to separate agents and checking their results. It uses an isolated Git worktree, a separate working copy of the project, to keep changes contained.

In plain words
What is it for?
Use it to execute a prepared plan, delegate coding and tests to agents, review their verdicts, and keep records such as plans, reviews, and audit logs.
Why use it?
It removes the need to coordinate every implementation and validation step yourself. It also adds checks between steps so later work does not continue after an earlier failure.

Skill for Claude CodeCodex

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/backspace-shmackspace/claude-devkit/ship
Any agent
npx skills add backspace-shmackspace/claude-devkit --skill ship
Clone the repo
git clone --depth 1 https://github.com/backspace-shmackspace/claude-devkit

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 19,127 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.19127
Opus 5 $0.00008 $0.09564
Sonnet 5 $0.00003 $0.03825
Haiku 4.5 $0.00002 $0.01913

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

Security

Grade D, and why

ship scanned grade D with 3 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

chmod 600 "$KEY_FILE"

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

SECRETS_SCAN_DEPLOYED=$(ls ~/.claude/skills/secrets-scan/SKILL.md 2>/dev/null && echo "yes" || echo "no")

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

echo " rm -rf /tmp/ship-*"
skills/ship/SKILL.md · 1,719 lines

How it starts

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

/ship Workflow

Inputs

  • Plan file: $ARGUMENTS # Full path, or bare plan name (e.g. "cross-repo-plan-support")

Output Rules

  • Always print full absolute paths for all artifact references (plan files, review files, audit logs). This makes paths clickable in terminals like Warp. Use the resolved $PLANS_DIR value, never relative paths.

Role

You are the work coordinator. You dispatch work to agents and check their results. You do NOT write code, explore the codebase, or run tests yourself — agents do that. Your job: read the plan once, dispatch each step, check verdicts, gate progression.

Step 0 — Pre-flight checks

Tool: Bash (git status, cleanup), Glob (agent checks) — Run all checks in parallel in a single message

Resolve devkit paths (MUST be first action in Step 0):

Tool: Bash

# --- Devkit Path Resolution ---
DEVKIT_SCRIPTS="${CLAUDE_DEVKIT:-$HOME/.claude-devkit}/scripts"

# Source path resolution helper
if [ -f "$DEVKIT_SCRIPTS/resolve-project-dir.sh" ]; then
  . "$DEVKIT_SCRIPTS/resolve-project-dir.sh"
  DEVKIT_PROJECT_DIR_RESOLVED=$(resolve_devkit_project_dir) || {
    echo "Failed to resolve project directory" >&2; exit 1
  }
elif [ -n "${DEVKIT_PROJECT_DIR:-}" ]; then
  DEVKIT_PROJECT_DIR_RESOLVED="$DEVKIT_PROJECT_DIR"
else
  echo "WARNING: devkit is not installed. Using deprecated .devkit/ fallback." >&2
  DEVKIT_PROJECT_DIR_RESOLVED=".devkit"
fi

PLANS_DIR="$DEVKIT_PROJECT_DIR_RESOLVED/plans"
mkdir -p "$PLANS_DIR"
echo "Plans directory: $PLANS_DIR"

Resolve plan path (MUST be second action in Step 0):

If $ARGUMENTS (after removing any flags like --security-override) does not contain a / character, treat it as a bare plan name and resolve it to $PLANS_DIR/<name>.md. If the name already ends with .md, do not append it again. Verify the resolved file exists; if not, try without .md suffix removed (in case the user passed e.g. feature.md). If neither exists, halt with: "Plan not found: tried $PLANS_DIR/.md"

Read the full file on GitHub · 1,719 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.

  1. 2d ago First seen · 1,719 lines · 16 tokens per session scan D f8d7974d2d1b

Subscribe to this mod's changes

ship is a skill published in the GitHub repository backspace-shmackspace/claude-devkit (15 stars, last pushed 9d ago), licensed MIT. It adds 16 tokens to every session and 19,127 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, enumerates other installed skills, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

create-modal

Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.

marcus/sidecar · 69 tokens

worktree-switching

Git worktree support in sidecar: worktree detection, switching between worktrees, worktree state management, and plugin reinitialization. Covers the full lifecycle of worktree context switching including registry reinit, per-worktree state persistence, deleted worktree detection and fallback. Use when working on git…

marcus/sidecar · 74 tokens

autoprompt

Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.

Spielewoy/autoprompt-skill · 56 tokens

ap-fresh-verifier

L4 blind fresh verifier - independently checks a candidate roadmap or plan against the exact mission and repository; APPROVE/REJECT, default-FAIL.

Spielewoy/autoprompt-skill · 36 tokens

cron

Schedule reminders and recurring tasks.

Peiiii/nextclaw · 8 tokens

agenticx-query-data-source

Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.

DemonDamon/AgenticX · 49 tokens