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.
npx skills add juanmhidalgo/claude-plugins --skill shipgit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/ship)<a href="https://agentmods.dev/skills/juanmhidalgo/claude-plugins/ship"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/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/juanmhidalgo/claude-plugins/ship"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/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.00105 | $0.04011 |
| Opus 5.5 | $0.00042 | $0.01604 |
| Sonnet 5.5 | $0.00021 | $0.00802 |
| Haiku 4.5 | $0.00011 | $0.00401 |
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 today.
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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Workflow
Execute these phases in order. Stop and report at any failure.
Context
- Branch: !
git branch --show-current - Remote tracking: !
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "no upstream" - Uncommitted changes: !
git status --short | head -20 - Arguments: $ARGUMENTS
When you invoked this skill from the conversation rather than the user typing /ship, read the flags from what the user said: "as a draft" → --draft, "no PR" → --no-pr, "skip tests" → --skip-tests, "don't wait" / "no need to watch CI" → --no-watch. Anything not mentioned keeps its default.
Phase 1: Status & Branch Detection
- Run
git status(never use-uall) - Run
git diff --statfor unstaged changes summary - Run
git diff --cached --statfor already-staged changes - Detect the repo's default branch:
gh repo view --json defaultBranchRef -q .defaultBranchRef.name 2>/dev/null || echo "main" - Detect branch type:
- Default branch (main, master, prod, or whatever the repo uses) → ask about branching (see below)
- Feature branch: anything else → PR workflow
If there are no changes (working tree clean, nothing staged), stop and inform the user.
If on the default branch, ask user with AskUserQuestion:
- "Create a new feature branch" — auto-generate a descriptive branch name from the changes (e.g.,
fix/null-check-auth-middleware,feat/add-billing-export). Use the conventional commit type as prefix. Create withgit checkout -b <name>. - "Continue on current branch" — proceed with direct push workflow
If the user creates a new branch, the rest of the workflow follows the feature branch path (PR offered at the end).
Phase 2: Smart Staging
If there are unstaged changes:
- List all changed and untracked files
- Exclude secrets automatically: skip
.env, credentials, tokens, private keys — warn the user about excluded files - Analyze change cohesion — determine if all changes relate to a single concern or multiple:
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.
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.
- today Changed · +1 lines cf99ea34ad18
- 17d ago Changed · +14 lines 59896eed78df
- 25d ago Changed · +27 lines · +69 tokens per session 989bd6147b11
- 1mo ago Changed · -4 lines 8ccab03a0266
- 1mo ago First seen · 245 lines · 36 tokens per session scan A 67d75fe596ca
ship is a skill published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 4,011 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
jig-conformance-audit
Use to check whether a repository's history actually followed the jig procedure: conventional squash subjects, Release-Grade trailers on unreleased work, version tag format and placement, the main/develop fast-forward invariant, and a committed rubric. Read-only, exits non-zero on violations, and runs in CI.
semantic-release-convention-skill
Source of truth for commit-to-PR-to-merge-to-release conventions — semver labels, branch-aware tagging, changelogs, release pipelines.
mk:ship
Ship workflow with explicit scopes: prepare stages and commits locally; release pushes and creates a PR; publish manages issues and versioning. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying. Supports…