A workflow for delivering an OpenSpec change, where OpenSpec is the project's format for describing proposed code changes, after implementation is complete. It prepares the change, commits and pushes it, opens a pull request, and follows its automated checks and review.

Use it to finish an implemented OpenSpec change, update its tasks and specifications, create a pull request against the development branch, monitor CI, and handle safe follow-up fixes.

It brings the remaining delivery steps into one process instead of requiring you to track them manually. It also checks that the change is ready and responds to safe problems found by checks or review.

ship-change — Skill for Claude Code and Codex by BlackBeltTechnology

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.

Any agent

npx skills add BlackBeltTechnology/pi-agent-dashboard --skill ship-change

Clone the repo

git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard

Made for: Claude Code, Codex.

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/blackbelttechnology/pi-agent-dashboard/ship-change/github.svg)](https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/ship-change)

Your own site

<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/ship-change"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/ship-change/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/ship-change"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/ship-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 4,051 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00129	$0.04051
Opus 5	$0.00064	$0.02025
Sonnet 5	$0.00026	$0.00810
Haiku 4.5	$0.00013	$0.00405

Measured 10d ago against content hash fb4896b2826a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade C, and why

ship-change scanned grade C with 1 finding 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 10d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"$parent/.worktrees/"*) rm -rf "$wt" ;; # confined to the .worktrees/ subtree

.pi/skills/ship-change/SKILL.md · 292 lines

How it starts

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

ship-change

End-to-end "land it" pipeline for an OpenSpec change. Runs after openspec-apply has implemented the code. Orchestrates existing pieces — does not reimplement them.

Repo conventions (this project)

Base branch: develop.
Worktree path: .worktrees/os-<change>, branch os/<change>.
Remote: origin → github.com:BlackBeltTechnology/pi-agent-dashboard.
CI scripts: npx tsx ./scripts/list-recent-runs.ts [--failed], scripts/show-failed-run.ts <run-id>.
OpenSpec skills resolve from the parent repo root when running inside a worktree (per AGENTS.md), not the worktree checkout.

Preconditions (verify, do not assume)

openspec-apply finished; all non-QA/manual tasks are checked.
Working tree builds and tests pass (this skill re-verifies).
gh auth status succeeds; git remote get-url origin resolves.

Resolve the change name from the worktree dir basename (os-<change> → <change>) or openspec list --json. Announce: "Shipping change: <change>". If ambiguous, ask.

Procedure

1. Mark deferrable tasks done (manifest-aware, legacy fallback)

Read openspec/changes/<change>/tasks.md. List remaining - [ ] tasks. The defer rule reads the manifest (test-plan.md) when present, else falls back to the legacy keyword rule. Pure logic: .pi/skills/ship-it/scripts/manifest.ts → deferDecision(tasks, manifestText).

Precedence:

openspec/changes/<change>/test-plan.md exists (manifest-era change): a leftover - [ ] is deferrable only if it maps to a manual-only manifest row — either an inline (test-plan: manual-only) tag or a (test-plan #<id>) reference resolved against the manifest. Any other leftover = real work = STOP. Automated scenarios are never deferred — they are proven done (harness-verified) before ship, so they are already - [x]. Flip each deferrable - [ ] → - [x] (validated post-merge).
test-plan.md absent (legacy change): fall back to today's keyword defer, unchanged — all remaining unchecked tasks whose body matches (case-insensitive) qa, manual, verify, smoke, test by hand, e2e, acceptance → flip to - [x]; any non-matching leftover → STOP.

Read the full file on GitHub · 292 lines

Files

What ships with it

2 files 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.

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.

10d ago First seen · 292 lines · 129 tokens per session scan C fb4896b2826a

Subscribe to this mod's changes

ship-change is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (278 stars, last pushed today), licensed MIT. It adds 129 tokens to every session and 4,051 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Commits Git and workflow Releases agent agent-framework agent-orchestration agent-skills agentic agentic-ai

akigitcommit

Analyze the working tree and commit changes in clean logical groups. Triages a long half-finished tree first (finished vs mid-edit vs abandoned vs accidental) before grouping. Auto-detects CHANGELOG to switch between domain-grouped mode (3–5 commits by object/feature) and type-grouped mode (feat/fix/refactor). Stages…

lacvietanh/akidevrule · 100 tokens

akiship

Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION IS LITERAL: this skill runs only on a user turn containing the exact token /akiship that asks for the run to be performed. Nothing else activates it — not the bare word "akiship", not a release-flavored paraphrase, and never a…

lacvietanh/akidevrule · 0 tokens

agency-jira-workflow-steward

Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.

BlackPearl-AI/BlackPearl-CodingAgent · 38 tokens

git-integration

Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.

a5c-ai/babysitter · 39 tokens

public-plugin-packaging

Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.

agentlas-ai/Agentlas-OS · 34 tokens

commit

Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.

congchuanling-dot/Cohort · 59 tokens

ship-change

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade C, and why

Recursive force deletehighDestructive command

How it starts

ship-change

Repo conventions (this project)

Preconditions (verify, do not assume)

Procedure

1. Mark deferrable tasks done (manifest-aware, legacy fallback)

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

akigitcommit

akiship

agency-jira-workflow-steward

git-integration

public-plugin-packaging

commit