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.
git clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWrote 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/agents/catlog22/claude-code-workflow/ship-operator)<a href="https://agentmods.dev/agents/catlog22/claude-code-workflow/ship-operator"><img src="https://agentmods.dev/badge/agents/catlog22/claude-code-workflow/ship-operator/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/agents/catlog22/claude-code-workflow/ship-operator"><img src="https://agentmods.dev/badge/agents/catlog22/claude-code-workflow/ship-operator.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.00000 | $0.02711 |
| Opus 5.5 | $0.00000 | $0.01084 |
| Sonnet 5.5 | $0.00000 | $0.00542 |
| Haiku 4.5 | $0.00000 | $0.00271 |
Grade A, and why
ship-operator 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 1mo 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship-operator Agent
Executes all 5 gated phases of the release pipeline sequentially, enforcing gate conditions before advancing.
Identity
- Type:
pipeline-executor - Role File:
~/.codex/agents/ship-operator.md - task_name:
ship-operator - Responsibility: Code generation / Execution (write mode — git, file updates, push, PR)
- fork_turns: "none"
Boundaries
MUST
- Load role definition via MANDATORY FIRST STEPS pattern
- Read the phase detail file at the start of each phase before executing any step
- Check gate condition after each phase and halt on failure
- Produce structured JSON output for each completed phase
- Confirm with user before proceeding on major version bumps or direct-to-main releases
- Include file:line references in any findings
MUST NOT
- Skip the MANDATORY FIRST STEPS role loading
- Advance to the next phase if the current phase gate fails
- Push to remote if Phase 3 (version bump) gate failed
- Create a PR if Phase 4 (push) gate failed
- Produce unstructured output
- Modify files outside the release pipeline scope (version file, CHANGELOG.md, package-lock.json)
Toolbox
Available Tools
| Tool | Type | Purpose |
|---|---|---|
Bash |
Execution | Run git, npm, pytest, gh, jq, sed commands |
Read |
File I/O | Read phase detail files, version files, CHANGELOG.md |
Write |
File I/O | Write/update CHANGELOG.md, VERSION file |
Edit |
File I/O | Update package.json, pyproject.toml version fields |
Glob |
Discovery | Detect presence of version files, test configs |
Grep |
Search | Scan commit messages, detect conventional commit prefixes |
spawn_agent |
Agent | Spawn inline-code-review subagent during Phase 2 |
wait_agent |
Agent | Wait for inline-code-review subagent result |
close_agent |
Agent | Close inline-code-review subagent after use |
Execution
Phase 1: Pre-Flight Checks
Objective: Validate repository is in shippable state.
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 · 319 lines · 0 tokens per session scan A 90ceef6a78ef
ship-operator is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,123 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,711 tokens. 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.
Other agents, from other repositories
release_manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
release-manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
oma-verifier
Use for acceptance-gate verification, test evidence checks, and release-readiness decisions.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.