ship

ship is a skill for Claude Code, Codex from mr-daedalium/ostack-saas. It costs 72 tokens per session (18,082 once invoked), scanned A, original, MIT.

A workflow for finishing and sharing code changes from a Git repository, a project that tracks file history. It includes merging the base branch, testing, reviewing changes, updating version and changelog files, committing, pushing, and opening a pull request.

In plain words
What is it for?
Use it when code is ready to ship, deploy, push to the main branch, or turn into a pull request.
Why use it?
It brings the separate release steps into one repeatable process and helps catch problems before changes are shared. A pull request is a proposed set of changes for review before merging.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also runs codex exec. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Good fit Use it when code is ready to ship, deploy, push to the main branch, or turn into a pull request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mr-daedalium/ostack-saas/ship
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.

Any agent
npx skills add mr-daedalium/ostack-saas --skill ship
Clone the repo
git clone --depth 1 https://github.com/mr-daedalium/ostack-saas

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ship

README.md
[![agentmods](https://agentmods.dev/badge/skills/mr-daedalium/ostack-saas/ship/github.svg)](https://agentmods.dev/skills/mr-daedalium/ostack-saas/ship)
Your own site
<a href="https://agentmods.dev/skills/mr-daedalium/ostack-saas/ship"><img src="https://agentmods.dev/badge/skills/mr-daedalium/ostack-saas/ship/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ship

Your own site · 80×15
<a href="https://agentmods.dev/skills/mr-daedalium/ostack-saas/ship"><img src="https://agentmods.dev/badge/skills/mr-daedalium/ostack-saas/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 18,082 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00072 $0.18082
Opus 5 $0.00036 $0.09041
Sonnet 5 $0.00014 $0.03616
Haiku 4.5 $0.00007 $0.01808

Measured 9d ago against content hash 7d7deb9b1e05, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ship 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 9d 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

  • ship — 91% identical, 284 lines differ
  • ship — 84% identical, 507 lines differ
  • ship — 81% identical, 942 lines differ
  • review — 81% identical, 1,329 lines differ
  • ship — 80% identical, 636 lines differ
  • review — 77% identical, 1,204 lines differ
  • gs:ship — 75% identical, 1,386 lines differ
  • review — 73% identical, 1,391 lines differ
ship/SKILL.md · 1,433 lines

How it starts

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

Preamble (run first)

_UPD=$(~/.claude/skills/ostack/bin/ostack-update-check 2>/dev/null || .claude/skills/ostack/bin/ostack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
mkdir -p ~/.ostack/sessions
touch ~/.ostack/sessions/"$PPID"
_SESSIONS=$(find ~/.ostack/sessions -mmin -120 -type f 2>/dev/null | wc -l | tr -d ' ')
find ~/.ostack/sessions -mmin +120 -type f -delete 2>/dev/null || true
_CONTRIB=$(~/.claude/skills/ostack/bin/ostack-config get ostack_contributor 2>/dev/null || true)
_PROACTIVE=$(~/.claude/skills/ostack/bin/ostack-config get proactive 2>/dev/null || echo "true")
_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
echo "BRANCH: $_BRANCH"
echo "PROACTIVE: $_PROACTIVE"
source <(~/.claude/skills/ostack/bin/ostack-repo-mode 2>/dev/null) || true
REPO_MODE=${REPO_MODE:-unknown}
echo "REPO_MODE: $REPO_MODE"

If PROACTIVE is "false", do not proactively suggest ostack skills — only invoke them when the user explicitly asks. The user opted out of proactive suggestions.

If output shows UPGRADE_AVAILABLE <old> <new>: read ~/.claude/skills/ostack/ostack-upgrade/SKILL.md and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If JUST_UPGRADED <from> <to>: tell user "Running ostack v{to} (just updated!)" and continue.

AskUserQuestion Format

ALWAYS follow this structure:

  1. Recommendation: "Do X because Y." One sentence. Position first.
  2. Options: A) ... B) ... — two options, three max if genuinely needed. When an option involves effort, show both scales: (human: ~X / CC: ~Y)

Skip AskUserQuestion entirely if there's a clear right answer — just do it and report.

Never hedge. Never pad with "great question." Never restate context the user already has. Compress ruthlessly. Trust the user to keep up.

Read the full file on GitHub · 1,433 lines

Files

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.

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. 9d ago First seen · 1,433 lines · 72 tokens per session scan A 7d7deb9b1e05

Subscribe to this mod's changes

ship is a skill published in the GitHub repository mr-daedalium/ostack-saas (110 stars, last pushed 5mo ago), licensed MIT. It adds 72 tokens to every session and 18,082 once invoked, about $0.0004 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-30.