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 TweekFawkes/prompts --skill shipgit clone --depth 1 https://github.com/TweekFawkes/promptsWrote 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/tweekfawkes/prompts/ship)<a href="https://agentmods.dev/skills/tweekfawkes/prompts/ship"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/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/tweekfawkes/prompts/ship"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/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.00134 | $0.03362 |
| Opus 5 | $0.00067 | $0.01681 |
| Sonnet 5 | $0.00027 | $0.00672 |
| Haiku 4.5 | $0.00013 | $0.00336 |
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 9d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship — Commit, PR, merge, and prove this worktree is safe to delete
Run this inside the feature worktree, after /dowork has finished (or after any other change you're ready to land).
Goal: every change in this worktree lands on main through a merged GitHub PR, the main checkout is current, and you can state plainly whether deleting the worktree would lose anything. You do the merge; the user deletes the worktree.
This does the same job as /landtomain, tuned for the /newticket → /dowork → /ship pipeline: it expects (but doesn't require) a ticket that just moved to z_tickets/closed/, and it fast-forwards main correctly even when main is checked out in a different worktree than this one — the normal setup once you're running multiple worktrees off one repo (see /gitready). If your worktree setup always keeps main checked out right here, /landtomain and /ship behave identically; pick whichever name matches your muscle memory.
--pr-only: stop cleanly after phase 4 (PR open, nothing merged) and say so. Use it when the PR should sit for review. Everything after phase 4 is skipped, including phase 7.
Work the phases in order. Stop and ask if any phase fails or surfaces something unexpected — a merge to main and the delete that follows are hard to walk back.
Authoritative facts (verify, don't assume)
- Remote:
origin→ your GitHub repo. Confirm withgit remote -v. - Base branch:
main. Main checkout: discover it, don't hardcode. Two shapes are common:- Linked worktrees off one shared repo (what
/gitreadysets up):mainstays checked out in one worktree — usually the original clone — while every task gets its own linked worktree on a feature branch.git checkout mainfrom a linked worktree fails ("already used by worktree at …") because git refuses to have the same branch checked out twice. Find the worktree withmainchecked out viagit worktree list --porcelain(the entry whosebranchline readsrefs/heads/main) and run anything that touches localmainasgit -C "$MAIN_WT" …. - A single checkout, branch-switching in place: there is no separate
mainworktree —git checkout mainworks directly. The commands below handle both; the worktree-list lookup simply comes back empty and you fall back to a plain checkout.
- Linked worktrees off one shared repo (what
- CLI: use
ghfor all GitHub operations. Never hand-craft API calls. - Branch naming: feature branches follow your convention (e.g.
<username>/<slug>); agent branches may becodex/<slug>orclaude/<slug>. Use whatever branch is checked out — never rename it. - Merge style: a merge commit —
gh pr merge <n> --merge. Not squash, not rebase, so the PR title becomes the merge subject. Write the title as the real change summary. (Use squash/rebase instead if that's your repo's convention — just be consistent with your last few merges.) - Worktree gitignored artifacts: env files, dependency caches, and other seeded-but-ignored local state never appear in
git status, are never force-added, and are never "lost work" — they're reproducible. - What deleting a worktree actually loses: only things that exist solely in this working tree and aren't on
main— uncommitted changes, untracked non-ignored files (e.g. a newz_tickets/**file), and unmerged local commits. Stashes live in the shared.gitand survive the delete, but still report them.
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.
- 9d ago First seen · 205 lines · 134 tokens per session scan A c7a6b8aba352
ship is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 134 tokens to every session and 3,362 once invoked, about $0.0007 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 skills, from other repositories
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.