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 agentmods add skills/phase-rs/phase/ship-commitsnpx skills add phase-rs/phase --skill ship-commitsgit clone --depth 1 https://github.com/phase-rs/phaseWhat 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.00115 | $0.04025 |
| Opus 5 | $0.00057 | $0.02013 |
| Sonnet 5 | $0.00023 | $0.00805 |
| Haiku 4.5 | $0.00012 | $0.00402 |
Grade A, and why
ship-commits 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 3d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Commits
Take local commits and land them on main through the merge queue, using an isolated worktree to avoid carrying other agents' concurrent work into the PR.
Why a worktree
The main working dir is assumed to contain other unrelated changes from concurrent agents — unstaged work, other branches, in-progress commits on main that aren't yet shipped. Branching in place risks:
- Carrying unrelated commits into the PR (if local
mainis ahead oforigin/mainwith multiple agents' work). - Disturbing other agents' branch state with
git checkoutoperations. - Leaving the user on a topic branch they didn't expect to be on.
A worktree based on origin/main gives a clean branch we cherry-pick into, isolated from everything else.
When to use
- User has finished a discrete chunk of work and wants it shipped.
- One or more commits exist locally (named explicitly, or "the last N commits on main", or "this commit").
- Goal: branch → push → PR → enqueue, with the queue handling rebase + CI + merge in the background.
When NOT to use
- Work is uncommitted. Run
/commitfirst (commit by pathspec — your memory'sfeedback_shared_index_commit_pathspec). Uncommitted work being shipped must not be left dirty on localmain. - A PR for these commits already exists. Use
gh pr merge <N> --autodirectly to enqueue. - The commits are already on
origin/main. Nothing to do. - Repo isn't
phase-rs/phase. This skill encodes phase.rs-specific conventions.
Phase.rs-specific conventions
| Convention | Why |
|---|---|
The merge queue owns the merge strategy — do NOT pass --squash. gh pr merge --squash --auto is rejected with The merge strategy for main is set by the merge queue. Pass --auto alone. The queue still produces a squash commit, which is why Step 0's reconciliation must stay squash-aware. |
Repo keeps main as one-commit-per-feature, enforced queue-side rather than client-side. |
--auto is mandatory on gh pr merge. |
Without it, the merge bypasses the queue and tries to merge immediately — fails on protected main. |
--no-verify on push. |
Pre-push hooks duplicate validation that Tilt/CI has already done locally. CI/queue will re-validate. |
Branch protection on main blocks direct push for non-admins. |
Queue handles serialization for parallel PRs. |
| Worktree-based shipping. | Main working dir has concurrent changes from other agents — don't disturb 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.
- 3d ago First seen · 285 lines · 115 tokens per session scan A 0858189f42bd
ship-commits is a skill published in the GitHub repository phase-rs/phase (259 stars, last pushed 3d ago), licensed Apache-2.0. It adds 115 tokens to every session and 4,025 once invoked, about $0.0006 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.
Other skills, from other repositories
ship
Ship current branch to main — commit, push, update from origin/main, merge, cleanup. Use when done with a feature/fix branch.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
release
Create a new es-toolkit release (version bump, changelog, tag).
git-workflow
安全处理 Git 状态检查、提交信息、commit、分支、push、PR 和 rebase。用于用户要求检查改动、生成或创建提交、管理分支、推送、发起 PR 或整理历史时；严格区分每个动作的授权，并保护工作树中已有和无关的修改。.