A workflow skill for taking a pull request from local verification through merging. A pull request is a proposed set of code changes submitted for review before it enters the main branch.

Use it for requests such as “ship,” “ship it,” or “push and merge” when the code should go through the complete pull-request process.

It coordinates pushing changes, creating or updating the pull request, checking automated tests, responding to review feedback, and merging without administrative override.

ship — Skill for Claude Code and Codex by gopherguides: A workflow skill for taking a pull request from…

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/gopherguides/gopher-ai/ship

Any agent

npx skills add gopherguides/gopher-ai --skill ship

Clone the repo

git clone --depth 1 https://github.com/gopherguides/gopher-ai

Made for: Claude Code, Codex.

Or install go-workflow, the plugin that ships this one along with the rest of its 10 skills, 3 commands, 4 agents, 4 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gopherguides/gopher-ai/ship.svg)](https://agentmods.dev/skills/gopherguides/gopher-ai/ship)

Your own site

<a href="https://agentmods.dev/skills/gopherguides/gopher-ai/ship"><img src="https://agentmods.dev/badge/skills/gopherguides/gopher-ai/ship.svg" alt="Measured on agentmods" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 7,189 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.00063	$0.07189
Opus 5	$0.00032	$0.03594
Sonnet 5	$0.00013	$0.01438
Haiku 4.5	$0.00006	$0.00719

Measured today against content hash 12f9b1c77011, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

plugins/go-workflow/skills/ship/SKILL.md · 609 lines

How it starts

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

Ship PR

Plugin Resource Resolution

<PLUGIN_ROOT> is notation. Replace it with a concrete absolute plugin root before every resource read or command:

Codex: Start from the directory containing the absolute selected SKILL.md path, then ascend two directories (skills/<name> -> plugin root).
Claude Code: Bind it to the injected ${CLAUDE_PLUGIN_ROOT} value.

Before requesting decisions or delegating work, read <PLUGIN_ROOT>/lib/driver-interaction.md and follow its cross-platform capability-binding rules.

Read <PLUGIN_ROOT>/lib/decision-gates.md before resolving any workflow choice.

Bind the invocation arguments as SKILL_ARGS for $go-workflow:ship by reading <PLUGIN_ROOT>/lib/skill-arguments.md with this Claude Code compatibility payload: $ARGUMENTS

Load the shared GitHub REST helpers before any GitHub workflow operation:

source "<PLUGIN_ROOT>/lib/github-rest.sh"

GraphQL Budget Discipline (read first)

GitHub meters two separate hourly budgets: ~5,000 GraphQL points/hr and ~5,000 REST requests/hr. Tools that drive a GitHub Project board (e.g. Detent) already spend the GraphQL budget on ProjectV2 polling (Projects v2 is GraphQL-only). If this skill also leans on GraphQL for routine PR ops, the two collide and exhaust the shared pool — a CI-watch loop alone can burn hundreds of GraphQL points per PR. Keep routine PR work on the REST budget through the shared helper:

CI status / watch: use github_watch_pr_checks or github_check_snapshot, always pinned to the expected PR head SHA.
PR metadata: use github_current_pr and github_pr.
Formal reviews: use github_pr_reviews.
Mergeability: read REST .mergeable and .mergeable_state through github_pr.
Ordinary merge: use the REST pull merge endpoint with merge_method and the expected head SHA.

The only GraphQL exceptions in these workflows are review-thread discovery and resolution, closingIssuesReferences, and required merge-queue enqueueing. The sibling e2e-verify, address-review, and complete-issue skills source the same shared helper and follow this discipline.

Read the full file on GitHub · 609 lines

Files

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.

agents/openai.yaml 43 B

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.

today Changed · +13 lines 12f9b1c77011
4d ago First seen · 596 lines · 63 tokens per session scan A 05a0b3af25b4

Subscribe to this mod's changes

ship is a skill published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 7,189 once invoked, about $0.0003 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.

Code review DevOps and cloud Git and workflow

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens