Borrowing it
Nothing to install: this file belongs to wbern/agent-instructions. 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/wbern/agent-instructions/main/.claude/commands/pr-ship.mdgit clone --depth 1 https://github.com/wbern/agent-instructionsWrote 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/commands/wbern/agent-instructions/pr-ship)<a href="https://agentmods.dev/commands/wbern/agent-instructions/pr-ship"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/pr-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/commands/wbern/agent-instructions/pr-ship"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/pr-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.00015 | $0.00807 |
| Opus 5.5 | $0.00006 | $0.00323 |
| Sonnet 5.5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
pr-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 2mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship - Direct Merge to Main
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
Ship/Show/Ask Pattern - SHIP
Ship is for small, obvious changes that don't need code review. Examples:
- Typo fixes
- Formatting changes
- Documentation updates
- Obvious bug fixes
- Dependency updates with passing tests
Prerequisites
Before shipping directly to main:
- All tests must pass
- Linter must pass
- Changes must be small and low-risk
- CI must be green (if configured)
Workflow
Current branch status:
!git status
Recent commits:
!git log --oneline -5
User arguments:
Ship: $ARGUMENTS
End of user arguments
Process:
-
Verify Change Size: Check git diff to ensure changes are small and focused !
git diff --stat main -
Run Tests: Ensure all tests pass !
npm testor !yarn testor appropriate test command for the project -
Run Linter: Ensure code quality checks pass !
npm run lintor !yarn lintor appropriate lint command (if available) -
Safety Check: Confirm with user that this is truly a ship-worthy change:
- Is this a small, obvious change?
- Do all tests pass?
- Is CI green?
If ANY of these are "no", suggest using
/pr-showor/pr-askinstead. -
Merge to Main: If all checks pass and user confirms:
git checkout main git pull origin main git merge --ff-only [feature-branch] || git merge [feature-branch] git push origin main
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.
- 2mo ago First seen · 118 lines · 15 tokens per session scan A 9923c9c39143
pr-ship is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 807 once invoked, about $0.0001 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 commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.