A command that updates a workspace's maintenance scripts to match the newest shared template. It is the pull direction of a synchronization process, similar to pulling changes from a shared Git repository.

Use it to compare versions, update selected script components, preserve workspace-specific files, run shell and configuration checks, remove retired files, and update the workspace version marker.

It keeps workspace tooling aligned with the shared version while checking safety conditions and reporting files that older versions no longer use.

update — Command by anshss

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/update

Clone the repo

git clone --depth 1 https://github.com/anshss/shiploop

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

When invoked 4,058 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.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.04058
Opus 5	$0.00010	$0.02029
Sonnet 5	$0.00004	$0.00812
Haiku 4.5	$0.00002	$0.00406

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

Security

Grade A, and why

update 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/update.md · 289 lines

How it starts

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

/shiploop:update

The pull direction of the harness-code update channel — git pull for harness code. Reconciles this workspace against the latest installed hub, the ongoing-maintenance path after /shiploop:setup has scaffolded once. scaffold.sh is the machinery; this command wraps it with reachability resolution + safety guards + verification.

Procedure

Locate the hub (same priority as /setup, see "Locate the plugin" there).
Verify preconditions — meta-repo workspace, harness paths not dirty, no governor running.
Cheap version + diff check (writes nothing).
Component-by-component bump via scaffold.sh --component <name> --yes — PRESERVES scripts/lib/workspace.sh (never overwritten without explicit ask).
Run no-auth verifiers — config-check.sh + bash -n sweep + stale-relocations warning. The bump itself also purges retired files: every writer run applies templates/lib/purge.txt, so files an older shiploop installed and no longer ships are deleted from this workspace. Report what went, since a purge can remove something the operator was still opening by habit.
Update .harness-version stamp (scaffold does this every run).
Report a concise per-component in-sync | bumped | skipped summary.

Phase 0 — Locate the hub

Resolve HUB in priority order:

${CLAUDE_PLUGIN_ROOT} (plugin run)
${GOVERN_UPSTREAM_HARNESS_DIR} from scripts/lib/workspace.sh (operator's local fork clone)
~/.claude/skills/shiploop/ (legacy clone-into-skills)
Glob ~/.claude/plugins/**/shiploop/VERSION (plugin-cache install)

If none resolve, STOP and print:

Cannot locate the shiploop hub.

Options:
  - Install as a plugin (recommended):
      /plugin marketplace add anshss/shiploop
      /plugin install shiploop@shiploop
  - Point at a local clone by exporting one of:
      CLAUDE_PLUGIN_ROOT=/path/to/shiploop   (env)
      GOVERN_UPSTREAM_HARNESS_DIR=/path/to/shiploop   (workspace.sh)

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

2d ago First seen · 289 lines · 0 tokens per session scan A e1dc3fb8977d

Subscribe to this mod's changes

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

Autonomous Agents Git and workflow ai-agents claude-code claude-code-plugin developer-tools git-worktrees

update

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/shiploop:update

Procedure

Phase 0 — Locate the hub

What this file has done since we first saw it

Other commands, from other repositories

fest-show

logs

review

browser

types

swarm-planner