ship

ship is a skill for Claude Code from natthasath/natthasath-marketplace. It costs 48 tokens per session (657 once invoked), scanned B, original, MIT.

A pre-merge checklist for a code branch. It checks types, linting, tests, code changes, project rules, task status, and acceptance criteria before merging.

In plain words
What is it for?
Use it to decide whether a branch is ready for a merge or pull request, where a pull request is a proposed change for review.
Why use it?
It catches failed checks and unfinished requirements before changes enter the main branch.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the projects plugin — 15 skills shipped together

Good fit Use it to decide whether a branch is ready for a merge or pull request, where a pull request is a proposed change for review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/natthasath/natthasath-marketplace/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 natthasath/natthasath-marketplace --skill ship
Clone the repo
git clone --depth 1 https://github.com/natthasath/natthasath-marketplace

Made for: Claude Code.

Or install projects, the plugin that ships this one along with the rest of its 15 skills.

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/natthasath/natthasath-marketplace/ship/github.svg)](https://agentmods.dev/skills/natthasath/natthasath-marketplace/ship)
Your own site
<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/ship"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/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/natthasath/natthasath-marketplace/ship"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 657 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00048 $0.00657
Opus 5.5 $0.00019 $0.00263
Sonnet 5.5 $0.00010 $0.00131
Haiku 4.5 $0.00005 $0.00066

Measured 19d ago against content hash f50bb3ecd4f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

ship scanned grade B with 1 finding 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 19d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

!`cat .claude/config/tech-stack.md 2>/dev/null`
plugins/projects/skills/ship/SKILL.md · 76 lines

What it actually says

!cat .claude/config/tech-stack.md 2>/dev/null

Pre-merge Ship Checklist

รัน pre-merge ship checklist สำหรับ branch ปัจจุบัน

Task ID (ถ้ามี): $ARGUMENTS

Core Rules (Non-negotiable)

  1. ต้องรัน technical checks จริงจาก command ใน tech-stack.md (typecheck/lint/test) ห้ามสมมติผลเอาเอง
  2. ห้ามรายงาน "✅ READY TO MERGE" จนกว่าจะตรวจครบทั้ง 4 ขั้นตอนและผ่านจริงทุกข้อใน Definition of Done
  3. ถ้ามี task ID ระบุมาใน $ARGUMENTS ต้องเช็ค acceptance criteria ของ task นั้นด้วยเสมอ ไม่ใช่แค่ technical checks

Workflow

1. Technical checks

ใช้ commands จาก tech-stack.md ด้านบน:

  • typecheck command
  • lint command
  • test command รายงาน: PASS/FAIL ต่อแต่ละอัน

2. Code review

  • รัน git diff main...HEAD เพื่อดูการเปลี่ยนแปลงทั้งหมด
  • ตรวจสอบเทียบกับ .claude/rules/ (coding-standards, security, performance)
  • รายงาน: มี blocking issues ไหม

3. Task tracking

  • เช็ค context/tasks/in_progress/current_sprint.md
  • task ของ branch นี้ถูก mark complete แล้วหรือยัง
  • ถ้าระบุ task ID ใน $ARGUMENTS ให้เช็ค acceptance criteria ด้วย

4. Self-check Definition of Done แล้วสรุปผล

ก่อนสรุปผล ให้ไล่ทวน checklist นี้ทีละข้อเทียบกับผลจริงจาก Step 1-3 (self-check) — ห้ามเดาว่าผ่านถ้ายังไม่เห็นผลจริง ข้อไหนยังไม่ผ่านให้ถือว่า NOT READY:

  • TypeScript/type errors: ไม่มี
  • Linter: zero warnings
  • Tests: ผ่าน
  • Acceptance criteria: verified

สรุปผล:

ถ้าผ่านทุก step:

─────────────────────────────────────────────────
✅ READY TO MERGE

ตัวเลือก:
  A) Merge local:
     git checkout main && git merge <branch> && git push

  B) เปิด Pull Request:
     git push -u origin <branch>
     แล้วเปิด PR บน GitHub/GitLab

ถัดไป → /done-task $ARGUMENTS   (mark task เสร็จ)
─────────────────────────────────────────────────

ถ้ายังมีปัญหา:

─────────────────────────────
❌ NOT READY — แก้ก่อน:
  · <สิ่งที่ต้องแก้>
─────────────────────────────
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. 19d ago Changed · +12 lines f50bb3ecd4f7
  2. 1mo ago First seen · 64 lines · 48 tokens per session scan B 8170aa8b0fd7

Subscribe to this mod's changes

ship is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 14d ago), licensed MIT. It adds 48 tokens to every session and 657 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.

Related

Other skills, from other repositories

security-architecture-review

Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…

cbrock84/headcount · 78 tokens

remove-ai-slops

Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.

code-yeongyu/oh-my-openagent · 45 tokens

code-review

Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a…

cbrock84/headcount · 72 tokens

completion-verification

Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of…

cbrock84/headcount · 73 tokens

codex-ab

Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict. Use when the branch is fresh, before any codex review runs.

oliver-kriska/claude-elixir-phoenix · 60 tokens

059-design-atdd

Use when reviewing whether an OpenSpec change's execution goal, acceptance criteria, and implementation or verification tasks are aligned. This should trigger for requests such as Review this OpenSpec change with ATDD; Check acceptance criteria against tasks; Find acceptance criteria without task coverage; Detect…

jabrena/plinth · 93 tokens