An orchestrator for shipping a qship epic, a larger piece of work made up of related tickets. It groups dependent tickets into waves, runs their work in parallel, merges results, and prepares final pull requests.

Use it to plan dependencies, execute tickets across one or more repositories, run wave-level checks and reviews, and create the final pull requests.

It coordinates multi-ticket delivery and checks each wave before the whole epic is delivered.

qshipmaster — Skill for Claude Code by 3awny/qship

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 3awny/qship --skill qshipmaster

Clone the repo

git clone --depth 1 https://github.com/3awny/qship

Made for: Claude Code.

Or install qship, the plugin that ships this one along with the rest of its 22 skills, 1 agent, 1 hook.

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/3awny/qship/qshipmaster/github.svg)](https://agentmods.dev/skills/3awny/qship/qshipmaster)

Your own site

<a href="https://agentmods.dev/skills/3awny/qship/qshipmaster"><img src="https://agentmods.dev/badge/skills/3awny/qship/qshipmaster/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/3awny/qship/qshipmaster"><img src="https://agentmods.dev/badge/skills/3awny/qship/qshipmaster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan D 3 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.00240	$0.19019
Opus 5.5	$0.00096	$0.07608
Sonnet 5.5	$0.00048	$0.03804
Haiku 4.5	$0.00024	$0.01902

Measured 1mo ago against content hash a99254619e2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade D, and why

qshipmaster scanned grade D with 3 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 1mo ago.

The scan reads SKILL.md. This mod also ships 9 executable files (hooks/qshipmaster-deliver.sh, hooks/qshipmaster-learn.sh, hooks/qshipmaster-merge-wave.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- `~/.claude/settings.json` or any settings file (user-owned).

Recursive force deletehighDestructive command

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

rm -rf {{STATE_ROOT}}/epic-{{JIRA_PROJECT_KEY}}-EX01

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| I1 | Wave N+1 MUST NOT spawn workers until Wave N's `wave-N-phase23-evidence.md` exists AND contains all 4 marker words (qsimplify, qcheck, qbug, qbcheck) AND contains a `## Phase 3 — /qe2etest evidence` section with a

templates/skills/qshipmaster/SKILL.md · 764 lines

How it starts

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

Issue source — tracker = {{TRACKER_TYPE}} (chosen at onboarding). Follow the issue-source protocol in $SKILLS_ROOT/qship/references/tracker-contract.md — it defines, per tracker, how to FETCH / CHILDREN / CREATE / TRANSITION / READ-TRD. For none: treat $ARGUMENTS as the spec (pasted text or a local file path) and skip all tracker MCP calls.

qshipmaster — Epic-level qship orchestrator

qship ships one ticket. qshipmaster ships an Epic.

This skill codifies the manual layer above qship: dependency-wave planning, per-wave parallel ticket execution, wave-level merging into a consolidated epic branch, wave-level Phase 2 review, and ONE consolidated PR per repo at the end.

Multi-repo contract: The set of repos this orchestrator coordinates across is $SKILLS_ROOT/qship/repos.json. The "one PR per repo" pattern below means one PR per entry in that list (or a subset of entries actually touched by the epic). Single-repo users see exactly one PR per epic. Multi-service monorepo users see N PRs, one per affected repo. Resolve the list at orchestrator startup:
ALL_REPOS=$(jq -r '.[].name' "$SKILLS_ROOT/qship/repos.json")

⛔ When this skill applies

Invoke qshipmaster when:

The argument is a Jira Epic (issuetype.name == "Epic").
You want fully unattended end-to-end Epic delivery.

Do NOT invoke for:

Standalone tickets (use qship directly).
A single Story under an Epic (use qship directly — the parent SKILL.md §Epic-Mode hooks will keep the worker from opening a per-ticket PR).
Re-running specific stages on an already-shipped Epic — read state.json directly and call the helper scripts manually.

⛔ Composition philosophy — DO NOT duplicate qship

qshipmaster is a thin orchestrator. It must:

Compose existing primitives, never re-implement them:
- qship-persist.sh runs the per-ticket pipeline (don't reinvent it).
- qship-compute-context.sh classifies the diff (don't reinvent it).
- require-phase3-evidence.sh / require-pipeline-complete.sh enforce gates (don't bypass them).
- qshipcheck decides per-ticket completion (don't second-guess it).
- code-review:code-review is the final-PR review skill (don't reinvent it).

Read the full file on GitHub · 764 lines

Files

What ships with it

11 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.

1mo ago First seen · 764 lines · 240 tokens per session scan D a99254619e2a

Subscribe to this mod's changes

qshipmaster is a skill published in the GitHub repository 3awny/qship (2 stars, last pushed 3mo ago), licensed MIT. It adds 240 tokens to every session and 19,019 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it D with 3 findings (reads agent configuration directories, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow Project management agent-skills ai-agents claude-code-plugin codex-cli developer-tools

merge-review

Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.

SethGammon/Citadel · 40 tokens

catchup

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

oliver-kriska/claude-elixir-phoenix · 48 tokens

backlog

Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…

umputun/cc-thingz · 96 tokens

jira

Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).

sd0xdev/sd0x-harness · 64 tokens

stale-proposals

Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…

gtapps/hermitd · 140 tokens

glab

Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.

NikiforovAll/claude-code-rules · 59 tokens

qshipmaster