Borrowing it
Nothing to install: this file belongs to richardthe3rd/cambridge-beer-festival-app. 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/richardthe3rd/cambridge-beer-festival-app/main/.claude/commands/ship-issues.mdgit clone --depth 1 https://github.com/richardthe3rd/cambridge-beer-festival-appWrote 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/richardthe3rd/cambridge-beer-festival-app/ship-issues)<a href="https://agentmods.dev/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues"><img src="https://agentmods.dev/badge/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues/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/richardthe3rd/cambridge-beer-festival-app/ship-issues"><img src="https://agentmods.dev/badge/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues.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.00605 |
| Opus 5 | $0.00008 | $0.00302 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
ship-issues 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Issues
Full plan → implement → review → fix → PR → watch cycle for one or more GitHub issues.
Usage: /ship-issues #270 #324 #355
Workflow
Work through these stages in order. Pause for user approval at each ✋ gate.
Stage 1 — Plan
Invoke /plan-issues for all issue numbers. Present plans. ✋ Wait for approval.
Stage 2 — Implement
For each approved plan, spawn an implementation agent with isolation: "worktree":
- Branch name:
fix/<issue-number>-<short-slug>(created inside the worktree) - Pass: phase steps, allowed-file manifest as a hard constraint, explicit "do not modify files outside this list"
- The agent must run
./bin/mise run checkbefore committing and push to its branch
Run all implementation agents in parallel.
After all agents complete, verify each branch:
git diff $(git merge-base main fix/<issue-number>-<short-slug>)..fix/<issue-number>-<short-slug> --stat
Confirm only planned files changed. ✋ Flag any drift before continuing.
Stage 3 — Review
Run /address-review across all fix branches. Apply fixup commits for clear findings. ✋ Ask about ambiguous ones.
Stage 4 — Push PRs
Create one PR per fix branch targeting main. PR body must include Fixes #<issue-number> to auto-close the issue on merge, plus a brief summary of changes. Subscribe to all PRs with mcp__github__subscribe_pr_activity.
Stage 5 — Watch
Monitor CI and review activity. For each event:
- Green CI on all checks → nothing to do
- Test/analyze failure → diagnose and push a fix commit
- Copilot/automated review comment → invoke
/address-reviewon that PR - Human review comment → surface to user if ambiguous, otherwise fix and push
The session ends when all PRs are green and have no unresolved review threads.
Notes
- Implementation agents use
isolation: "worktree"— this creates worktrees inside the repo at.claude/worktrees/, which is required for commit signing in the managed environment. - Fix branches target
maindirectly. The session branch (claude/session-*) is for session-level changes (AGENTS.md updates, etc.). - Always run
./bin/mise runcommands, never rawflutter— see AGENTS.md for the full command reference. - MCP tool parameters take plain strings — no
$(cat <<'EOF'...)heredoc syntax inbodyfields (see AGENTS.md → "GitHub MCP Notes").
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.
- 11d ago First seen · 58 lines · 15 tokens per session scan A 21ba1ae5e8af
ship-issues is a command published in the GitHub repository richardthe3rd/cambridge-beer-festival-app (2 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 605 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.
Other commands, from other repositories
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.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.