setup

A command for creating or upgrading a Shiploop workspace: a package-manager root that coordinates several independent Git repositories and shared development tools.

In plain words
What is it for?
Scaffolding a new multi-repository workspace or updating an existing one while preserving its configured package manager and development settings.
Why use it?
It removes the repeated manual setup needed for repositories, worktrees, task queues, automated ticket handling, and session hooks.

Command

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 commands/anshss/shiploop/setup
Clone the repo
git clone --depth 1 https://github.com/anshss/shiploop
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,038 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.00024 $0.07038
Opus 5 $0.00012 $0.03519
Sonnet 5 $0.00005 $0.01408
Haiku 4.5 $0.00002 $0.00704

Measured 2d ago against content hash fa6b5a0b6647, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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 2d 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.

commands/setup.md · 504 lines

How it starts

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

You are the meta-repo setup command. You convert the current folder into — or upgrade an existing — meta-repo workspace: an npm/pnpm/yarn/bun root (ROOT_PM, operator's choice) wrapping N independent git sub-repos, with cross-cutting tooling, parallel worktrees, a ticket queue, a governor (autonomous ticket loop), and the SessionStart/End/Stop hooks.

The full pattern is documented in the plugin's SKILL.md (read if you need context). All mechanical file writes are executed by scaffold.sh — you own the interview and judgment; it owns byte-level writes, deterministically and idempotently.

Locate the plugin

Templates and scaffold.sh live together. Resolve PLUGIN_ROOT in priority order:

  1. ${CLAUDE_PLUGIN_ROOT} (plugin run)
  2. ~/.claude/skills/shiploop/ (legacy clone-into-skills)
  3. ~/.claude/plugins/** cache lookup by plugin name

SCAFFOLD=$PLUGIN_ROOT/scaffold.sh.

Architecture (read once)

Every mechanism script sources ONE config file, scripts/lib/workspace.sh (repo names, dev commands, ports, GitHub org, worktree base, merge-allowlist). Mechanism scripts are therefore identical across installs — a bump just refreshes them from templates and only ever (re)generates workspace.sh. Never hand-edit a mechanism script; put the value in workspace.sh.

Interview doctrine — ONE pause

  1. Detect first, ask second. Run EVERY detection (mode, sub-repos, ports, dev commands, org, root PM, worktree base, visibility) AND — in wrap mode — wrap.sh --preflight BEFORE the first question. Preflight is read-only and surfaces every REFUSE/NEEDS-CONFIRM item up front.
  2. One batched interview. Ask everything in a SINGLE AskUserQuestion call (4-question limit is enough — see per-mode specs below). Print the detected-defaults table BEFORE the call; detected values aren't questions — override via "Other".
  3. Then run to completion without pausing. Legitimate post-interview stops are ONLY: wrap.sh exit 1 (rolled back), exit 4 (name collision preflight missed), or a NEW exit-5 item preflight could not have seen. Never re-ask something the interview covered.

Read the full file on GitHub · 504 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.

  1. 2d ago First seen · 504 lines · 24 tokens per session scan A fa6b5a0b6647

Subscribe to this mod's changes

setup is a command published in the GitHub repository anshss/shiploop (5 stars, last pushed 29d ago), licensed Apache-2.0. It adds 24 tokens to every session and 7,038 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.