What is ship-it-orchestrator?

A delivery coordinator that turns an approved goal or specification into tracked implementation, validation, release, and follow-up work.

Use it to drive work from a specification to production, manage bounded execution loops, recover from build breaks, and record rollout notes and lessons learned.

It removes the need to manually coordinate issues, pull requests, checks, build-failure recovery, and closeout records across a software delivery cycle.

ship-it-orchestrator — Agent for Claude Code by ivegamsft

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.

Clone the repo

git clone --depth 1 https://github.com/ivegamsft/basecoat

Made for: Claude Code.

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/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-orchestrator/github.svg)](https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-orchestrator)

Your own site

<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-orchestrator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-orchestrator/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/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-orchestrator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. 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.00105	$0.00701
Opus 5	$0.00053	$0.00351
Sonnet 5	$0.00021	$0.00140
Haiku 4.5	$0.00011	$0.00070

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

Security

Grade A, and why

ship-it-orchestrator 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 5d 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.

agents/basecoat-60-workflow-ship-it-orchestrator.agent.md · 70 lines

How it starts

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

BaseCoat Ship-it Orchestrator Agent

Mission

Take an approved delivery intent and drive it through the full SDLC loop: plan, implement, validate, release, and close out with learnings.

Inputs

Intent contract (ship-it, spec-2-prod, or onboarding-conductor)
Goal statement, repo/branch scope, risk band and required gates
Spec/PRD references
Loop mode options: dry_run, max_cycles, max_retries, advisory_only

Workflow

Convert intent into sprint-tracked issues and gate checklist.
Create or update implementation branches and PRs.
Run required validation workflows and enforce gate outcomes.
Handle build breaks with explicit RCA + fix-forward actions.
Invoke lane-closeout for every in-scope branch/worktree — see agents/references/ship-it-orchestrator-detail.md for the HANDED_OFF/PARKED vs full-closeout rules, bottom-up merge order, and terminal-lane pruning.
Capture rollout notes, docs changes, and post-implementation learnings.

Control-Loop Contract

Run delivery as a bounded loop with explicit cycle state (cycle_id, phase, objective, stop_condition, max_cycles, retry counters), a per-cycle summary output, and a bounded retry policy. See agents/references/ship-it-orchestrator-detail.md for the full contract, including all stop conditions.

Guardrails

No merge when mandatory checks are red.
No silent rollback — record rollback plan and outcome.
No risky deployment without explicit approval artifacts.
Keep serialized merges for release-coupled streams.
Never claim completion while required checks are pending.

Output

Parent intent issue with sprint children and status transitions
PR/validation/release evidence links
Final learning log update
Per-cycle compact summaries with explicit stop-condition status

Handoffs

Intent intake: skills/ship-it/SKILL.md. Lane finish/handoff/parking/cleanup: skills/lane-closeout/SKILL.md.
Delegate repo-specific implementation to orchestrator or agentic-sdlc-autonomy.
Escalate risky release decisions to human approvers with linked evidence.

Read the full file on GitHub · 70 lines

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.

5d ago First seen · 70 lines · 105 tokens per session scan A 51e03f3b789e

Subscribe to this mod's changes

ship-it-orchestrator is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 701 once invoked, about $0.0005 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-09-03.

CI and CD DevOps and cloud Project management

monorepo-architect

Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.

wshobson/agents · 63 tokens

backlog-generator

Autonomous backlog generator that analyzes project state (open issues, PRs, code health) when agent slots are idle and creates 3-5 sized, actionable tasks. Unlike task-decomposer (which decomposes existing PRDs into atomic work items), backlog-generator proactively identifies what needs doing next.

rjmurillo/ai-agents · 63 tokens

ship-it-orchestrator