agentmods.dev

ship

ship is a skill for Claude Code, Codex from poshan0126/dotclaude. It costs 32 tokens per session (1,020 once invoked), scanned A, original, MIT.

A guided workflow for committing changes, sending them to a remote code repository, and opening a pull request for review.

In plain words
What is it for?
Checking the worktree, reviewing recent commits, selecting files, committing staged changes, pushing them, and creating a pull request.
Why use it?
It organizes the final delivery steps and asks for confirmation before each external action.

Skill for Claude CodeCodex

not rated 860 +4 9d ago A scan 32 tokens original MIT
View the source file poshan0126/dotclaude
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/poshan0126/dotclaude/ship
Any agent
npx skills add poshan0126/dotclaude --skill ship
Clone the repo
git clone --depth 1 https://github.com/poshan0126/dotclaude

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/poshan0126/dotclaude/ship.svg)](https://agentmods.dev/skills/poshan0126/dotclaude/ship)
Your own site
<a href="https://agentmods.dev/skills/poshan0126/dotclaude/ship"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/ship.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,020 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.1 $0.00032 $0.01020
Opus 5 $0.00016 $0.00510
Sonnet 5 $0.00006 $0.00204
Haiku 4.5 $0.00003 $0.00102

Measured 6d ago against content hash 55cd321785ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 6d 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.

skills/ship/SKILL.md · 88 lines

How it starts

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

Ship the current changes through commit, push, and PR creation. Confirm with the user before each step using the AskUserQuestion tool.

Step 1: Scan

Current scan state (injected read-only below — no need to re-run these to gather it):

  • Status: !git -C "${CLAUDE_PROJECT_DIR:-.}" status --short 2>/dev/null || echo "(no git repo or no changes)"
  • Change summary: !git -C "${CLAUDE_PROJECT_DIR:-.}" diff --stat HEAD 2>/dev/null || echo "(no diff)"
  • Recent commit style: !git -C "${CLAUDE_PROJECT_DIR:-.}" log --oneline -5 2>/dev/null || echo "(no commits yet)"

For the full patch of a specific file before committing, run git diff -- <file> on demand (kept out of the injection to hold the render small).

  • Present a clear summary to the user:
    • Files modified
    • Files added
    • Files deleted
    • Untracked files
  • If there are no changes, tell the user and stop

Step 2: Stage & Commit

  • Propose which files to stage. Never stage these:
    • Secrets: .env*, *.pem, *.key, credentials.json
    • Lock files: package-lock.json, yarn.lock, pnpm-lock.yaml (unless intentionally updated)
    • Generated: *.gen.ts, *.generated.*, *.min.js, *.min.css
    • Build output: dist/, build/, .next/, __pycache__/
    • Dependencies: node_modules/, vendor/, .venv/
    • OS/editor: .DS_Store, Thumbs.db, *.swp, .idea/, .vscode/settings.json
  • Draft a commit message based on the changes, matching the repo's existing commit style
  • ASK the user to confirm or edit: show the exact files to stage and the proposed commit message
  • Only after confirmation: stage the files and create the commit
  • If the commit fails (e.g., pre-commit hook), fix the issue and try again with a NEW commit

Step 3: Push

  • Check if the current branch has an upstream remote
  • If not, propose creating one with git push -u origin <branch>
  • ASK the user to confirm before pushing
  • Only after confirmation: push to remote

Step 4: Pull Request

  • Check if a PR already exists for this branch (gh pr view. If it exists, show the URL and stop)
  • Analyze ALL commits on this branch vs the base branch (not just the latest commit)
  • Draft a PR title (under 72 chars) and body with:
    • Summary: 2-4 bullet points
    • Test plan: how to verify
  • ASK the user to confirm or edit the title and body
  • Only after confirmation: create the PR with gh pr create
  • Show the PR URL when done

Read the full file on GitHub · 88 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. 6d ago First seen · 88 lines · 32 tokens per session scan A 55cd321785ee

Subscribe to this mod's changes

ship is a skill published in the GitHub repository poshan0126/dotclaude (860 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 1,020 once invoked, about $0.0002 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.

CommitsGit and workflowReleases
Related

Other skills, from other repositories

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

crew-commit

Canonical commit workflow for Gas Town crew members: pre-flight checks, branch creation, gt commit with agent identity, push, and PR creation. Use when ready to commit and submit work for review.

gastownhall/gastown · 43 tokens

cherry-pick

Cherry-pick a commit from main to a Sui release branch, create the release PR, and report the PR URL.

MystenLabs/sui · 30 tokens

task-snapshot

Create a commit or tag snapshot only when explicitly requested for a milestone, reproducibility checkpoint, handoff, or pinned artifact.

marin-community/marin · 29 tokens

mflux-pr

Make a clean PR in mflux (inspect diff, quick verification, commit, push, open PR) using repo conventions.

mflux-community/mflux · 29 tokens

comet-safe-delivery

在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.

rpamis/comet · 78 tokens