Borrowing it
Nothing to install: this file belongs to JeremyDev87/codingbuddy. 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/JeremyDev87/codingbuddy/master/.claude/skills/ship/SKILL.mdgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/ship)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/ship"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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/jeremydev87/codingbuddy/ship"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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.00048 | $0.02109 |
| Opus 5.5 | $0.00019 | $0.00844 |
| Sonnet 5.5 | $0.00010 | $0.00422 |
| Haiku 4.5 | $0.00005 | $0.00211 |
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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Changes
Follow every step in order. Stop and report if any step fails.
Step 1: Parse Arguments and Determine Issue Context
Parse $ARGUMENTS for:
--fullflag: If present, run ALL workspace checks (matches CI exactly). Remove--fullfrom arguments before processing issue context.- Issue context: Remaining argument is an issue number or URL.
Check if issue context is provided:
-
With issue (
/ship 613or/ship --full 613):gh issue view <number> --json title,body,labelsUse the issue title and labels to inform branch name, commit message, and PR description.
-
Without issue (
/shipor/ship --full): Skip issue fetch. Derive context entirely from the changed files andgit diff. The user will be asked to confirm the commit message and PR title before proceeding.
Step 2: Check Working Tree
git status
git diff --stat
If there are no changes to ship, stop and inform the user.
Step 3: Detect Affected Workspaces
Run git diff --name-only (include both staged and unstaged changes) and classify changed files into workspaces:
| Path Pattern | Workspace | Checks |
|---|---|---|
apps/mcp-server/** |
codingbuddy |
lint, format:check, typecheck, test:coverage, circular, build |
packages/rules/** |
codingbuddy + rules-validation |
Above + ajv-cli validate + markdownlint-cli2 |
packages/claude-code-plugin/** |
codingbuddy-claude-plugin |
lint, format:check, typecheck, test:coverage, circular, build |
apps/landing-page/** |
landing-page |
lint, format:check, typecheck, test:coverage, check:circular, build |
.claude/**, .cursor/**, .antigravity/**, .codex/**, .github/**, scripts/** |
rules-validation only | ajv-cli validate + markdownlint-cli2 |
Docs-only changes: If changed files don't match any pattern above (e.g., docs-only, root config) AND --full is NOT set, skip all CI checks (including security) and proceed to Step 7.
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 First seen · 262 lines · 48 tokens per session scan A dab775d44d9b
ship is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 2,109 once invoked, about $0.0002 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-30.
Other skills, from other repositories
finish-task
Deprecated alias for close-task.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
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…
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.