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 ccevans/bobbycode --skill bobby-shipgit clone --depth 1 https://github.com/ccevans/bobbycodeWrote 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/ccevans/bobbycode/bobby-ship)<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-ship"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-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/ccevans/bobbycode/bobby-ship"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.02979 |
| Opus 5.5 | $0.00022 | $0.01192 |
| Sonnet 5.5 | $0.00011 | $0.00596 |
| Haiku 4.5 | $0.00006 | $0.00298 |
Grade A, and why
ship-pr 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 yesterday.
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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bobby Ship Skill
Creates PRs, waits for CI, merges, and deploys — end to end, with no separate opt-in phrase required. Deploy detection is repo-specific (see Deploy below): some repos need nothing beyond the merge, others need a promotion PR, a CLI command, or a publish step. Hard stops remain for anything genuinely risky (migrations, merge-order dependencies, missing CI) — those pause and ask a human rather than guessing.
Want PR-only, no merge? If the user says "just open the PR", "ship but don't merge", or similar, skip straight to After PR Creation and stop there — don't merge or deploy.
Before Starting
- Check learnings — Read
.claude/skills/bobby-ship/learnings.md+.claude/skills/bobby-ship/learnings.local.md - Check the queue — Run
bobby ticket list shippingto see what's ready
Pre-Flight Checks
1. Shipping Count Sanity Check
Run bobby ticket list shipping and count the tickets.
If more than 10 tickets are in shipping, STOP and ask the user:
"There are {N} tickets in shipping. Is this a batch release or were these bulk-migrated? Should I proceed with all of them?"
Do NOT proceed until the user confirms. A large number often means tickets were migrated in bulk without actual code changes.
2. Uncommitted Changes Gate
Run git status --short in each repo. If there are uncommitted source code changes (modified/new .js, .ts, .rb, .py, .css, .html, .json, .yml, etc.):
STOP — do not ship. Uncommitted changes mean a prior agent (build, review, or test) failed to commit its work.
For each affected ticket:
bobby ticket move {ID} buildbobby ticket comment {ID} --by bobby-ship "Returned to build: uncommitted changes detected. Files: {list}. Build agent must commit all work before shipping."
Then abort the ship process. The workflow will re-run build → review → test → ship with proper commits.
Ignore non-source artifacts (screenshots, CSVs, mockups, .skill files) — these are not blockers.
What ships with it
2 files 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.
- yesterday Changed · +81 lines · +3 tokens per session a3f2ea1da6aa
- 1mo ago First seen · 126 lines · 53 tokens per session scan A de009a011132
ship-pr is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 2,979 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-09-03.
Other skills, from other repositories
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
ship
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'.…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
ship
Push, open a PR, and watch CI; land mode merges and cleans branches. Triggers "ship it", "create PR", "babysit CI", "land it", "fix CI and merge".