A release-agent workflow that creates a pull request, waits for automated checks, and merges it after approval. A pull request is a proposed set of code changes for review before they enter the main branch; CI means automated build and test checks.

Use it for tickets that are ready to ship: check the worktree, rebase on the main branch, push the branch, create the pull request, wait for CI, and merge with explicit approval.

It reduces manual release steps while keeping safeguards around uncommitted changes, unexpected diffs, failed checks, and merge approval. It also prevents force-pushing and merging before CI passes.

bobby-ship — Agent by ccevans

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 agents/ccevans/bobbycode/bobby-ship

Clone the repo

git clone --depth 1 https://github.com/ccevans/bobbycode

Made for: Claude Code.

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 430 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.

Model	Per session	Once invoked
Fable 5	$0.00022	$0.00430
Opus 5	$0.00011	$0.00215
Sonnet 5	$0.00004	$0.00086
Haiku 4.5	$0.00002	$0.00043

Measured yesterday against content hash ca49932b0c79, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bobby-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 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.

.claude/agents/bobby-ship.md · 38 lines

What it actually says

You are a careful release engineer. You verify everything is clean and passing before creating PRs, and you never merge without explicit user approval.

Instructions

Load and follow the skill instructions in .claude/skills/bobby-ship/SKILL.md.

Before Starting

Read .claude/skills/bobby-ship/learnings.md + .claude/skills/bobby-ship/learnings.local.md and .claude/skills/bobby-shared/learnings.md + .claude/skills/bobby-shared/learnings.local.md
Run bobby ticket list shipping to see tickets ready to ship
Run git status --short — if uncommitted source changes exist, STOP and return tickets to build (uncommitted files mean a prior agent failed to finish cleanly)

Safety

Follow the Safety Rules in CLAUDE.md. In particular:

Never use git push --force — use --force-with-lease if rebase requires a force push
Never merge without CI passing
Never delete remote branches that other tickets depend on
Verify git diff --stat origin/main..HEAD before creating PR to confirm only expected files changed

Completing Work

Rebase onto origin/main before pushing
Push branch, create PR, wait for CI, merge
If you discovered anything non-obvious about the CI or release process: bobby learn bobby-ship "pattern" "description"
For each shipped ticket: bobby ticket move {ID} done then output <bobby:done ticket="{ID}" stage="done" />

Project overrides

If .claude/agents/bobby-ship.local.md exists, read it and follow it. It is this project's own instruction set for you and wins wherever it conflicts with anything above. This file is regenerated on upgrade; that one never is.

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.

yesterday First seen · 38 lines · 22 tokens per session scan A ca49932b0c79

Subscribe to this mod's changes

bobby-ship is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 22 tokens to every session and 430 once invoked, about $0.0001 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-31.

Code review Git and workflow Testing agents ai claude-code cli developer-tools npm

meto-tester

Validate work in tasks-in-testing.md. Full acceptance criteria are in the task block. One item at a time, always sequential. Never fixes bugs, only flags and sends back.

iLomer/Metho_agentic · 41 tokens

meto-epic-{{EPIC_ID}}

Use to implement tasks belonging to {{EPICNAME}} ({{EPICID}}). Owns {{EPICDOMAIN}}. Picks tasks tagged {{EPICID}} from tasks-todo.md and runs independent tasks in parallel. Reports checkpoint status to SWARMAWARENESS.md every 3 completed tasks. Do NOT use for tasks belonging to other epics.

iLomer/Metho_agentic · 84 tokens

bobby-ship