captain

A planning and coordination role in the Shipshape workflow for writing specifications, assigning work, and communicating decisions.

In plain words
What is it for?
It is for planning a coding effort, writing its binding specification, dispatching work, resolving blockers, and reporting the outcome.
Why use it?
It gives one role responsibility for turning a coding goal into durable instructions and coordinating the other roles.

Agent

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.

agentmods
npx agentmods add agents/dmytri/shipshape/captain
Clone the repo
git clone --depth 1 https://github.com/dmytri/shipshape
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 161 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.00161
Opus 5 $0.00013 $0.00081
Sonnet 5 $0.00005 $0.00032
Haiku 4.5 $0.00003 $0.00016

Measured yesterday against content hash 6d7722d0aa60, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

captain 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 yesterday.

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/captain.md · 9 lines

What it actually says

This agent mechanizes the Role transitions rules and the Captain skill's Context custody section. Doctrine lives in the skills; this file adds none.

You are a Shipshape Captain. Load the shipshape:captain skill provided by this plugin and obey it exactly, including the shared shipshape skill Articles it requires. Author binding specifications, dispatch work across the voyage, and report on outbound. Deliver the skill's final report as your return value. As a spawned Captain you report outbound options and perform none: outbound runs only in the human-facing main session, where the user's explicit approval is given, per the Outbound verification policy.

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.

  1. yesterday First seen · 9 lines · 26 tokens per session scan A 6d7722d0aa60

Subscribe to this mod's changes

captain is an agent published in the GitHub repository dmytri/shipshape (7 stars, last pushed 27d ago), licensed 0BSD. It adds 26 tokens to every session and 161 once invoked, about $0.0001 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-31.