Borrowing it
Nothing to install: this file belongs to dixus/claudeframework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dixus/claudeframework/main/.claude/skills/ship/SKILL.mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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.
[](https://agentmods.dev/skills/dixus/claudeframework/ship)<a href="https://agentmods.dev/skills/dixus/claudeframework/ship"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/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.
<a href="https://agentmods.dev/skills/dixus/claudeframework/ship"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00028 | $0.12947 |
| Opus 5.5 | $0.00011 | $0.05179 |
| Sonnet 5.5 | $0.00006 | $0.02589 |
| Haiku 4.5 | $0.00003 | $0.01295 |
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 1mo 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 — 643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate the full spec-to-commit pipeline for the feature described in $ARGUMENTS or in .claude/input/.
--dry-run mode: If $ARGUMENTS contains --dry-run, run only Steps 1–2 (questions + spec), then print a scope report and stop. No branch, no implementation, no commits. Use this to preview complexity and scope before committing to a full pipeline run.
--no-finalize mode: If $ARGUMENTS contains --no-finalize, run the full pipeline (spec → implement → review → fix → commit) but skip Step 7 entirely — neither gate nor push nor state change. The feature stays on its branch with all commits applied and checks passing, but is not merged and the work item stays in its current state. Used by /fleet to manage merges centrally.
--auto-finalize mode: If $ARGUMENTS contains --auto-finalize, skip the Step 7a finalize gate and go straight to push + state transition. Use only when you trust the pipeline output without a manual smoke-test (doc-only commits, trivial refactors, hotfixes under time pressure). Default is the gated flow — the user sees a summary and must confirm before anything is pushed or the ticket changes state.
--fast mode: If $ARGUMENTS contains --fast, force the fast path regardless of the automatic classifier (Step 0c). Skips spec, review, and fix loop — uses a single implement subagent. Use for tickets where the scope is clearly trivial and you want to save token cost.
--full mode: If $ARGUMENTS contains --full, force the full pipeline regardless of the automatic classifier. Use when the classifier would choose fast path but the ticket has subtle integration risks or architecture decisions.
Architecture: The main session is a thin orchestrator only — it never reads code files or accumulates implementation context. Each phase runs in a dedicated subagent with a clean context. The spec file, review file, and git diff are the handoff mechanism between phases.
Notation: <main> denotes the repo's default branch (main or master). Determine it once in Step 0 with git symbolic-ref --short refs/remotes/origin/HEAD (fallback: whichever of origin/main / origin/master exists) and use that name wherever <main> appears below.
Progress updates: After each subagent returns, print a one-line status update so the user can track progress. Use this format:
✓ Step N — <phase> complete. <key detail from subagent summary>
Examples: ✓ Step 2 — Spec complete. 7 files, 3 new. · ✓ Step 3 — Implementation complete. All checks pass. · ✓ Step 4 — Review: pass with fixes (2 major). · ✓ Step 4 — Fix cycle 1 complete. 2/2 issues resolved.
Main session (orchestrator — reads summaries only)
├── Step 0: branch setup → creates ticket branch (or stays on current branch)
├── Step 0b: ticket resolution → loads work item + comments from tracker (if configured), sets state
├── Step 0c: complexity classifier → sets fast_path=true/false from ticket signals + --fast/--full flags
│
│ [fast path — fast_path=true or --fast]
├── Subagent F: implement [fable] → reads ticket_context, implements directly, runs verify
│
│ [full pipeline — fast_path=false or --full]
├── Subagent A: spec [opus] → writes .claude/specs/<name>.md incl. ## Contract
├── Step 2b: decision review → reads spec "Decisions made by Claude" → user approval
├── Subagent B: implement [fable] → single subagent, returns summary
├── Subagent C: review [opus] → writes .claude/reviews/<name>-review.md
├── Subagent D: fix [opus if rework, sonnet if fixes]→ loop back to C
├── Step 4b: lesson graduation → moves mature lessons → archive + CLAUDE.md rule
├── Step 4c: integration check [opus] → cross-phase glue review (phased only)
│
│ [both paths rejoin here]
├── Step 5: contract gate → generic suite + every Contract verify command
├── Step 5b: changelog entry → writes changelog/<branch>.md (per-ticket, merge-conflict-free)
├── Subagent E: commit [sonnet]→ atomic commits on feature branch
├── Step 6b: tracker feedback → syncs derived fields, then at most one comment
├── Step 6d: upload changelog → attaches changelog/<branch>.md to the work item (if supported)
├── Step 7a: finalize gate → show summary + contract coverage + test hints, wait for user confirm
└── Step 7b: push + finalize → pushes branch to origin, updates ticket state
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.
- 1mo ago Changed · +189 lines dcec7bf59838
- 2mo ago First seen · 454 lines · 28 tokens per session scan A edc573470aa2
ship is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 12,947 once invoked, about $0.0001 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…