agentmods.dev

update

update is a command for Claude Code from anshss/shiploop. It costs 0 tokens per session (3,992 once invoked), scanned A, original, Apache-2.0.

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.

In plain words
What is it for?
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.
Why use it?
It keeps workspace tooling aligned with the shared version while checking safety conditions and reporting files that older versions no longer use.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the shiploop plugin — 2 skills, 7 commands, 3 agents shipped together

not rated 9repo changed 1mo ago A scan 0 tokens original Apache-2.0

Good fit 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.

Compare 6 commands from other repositories ↓
View source ↗ anshss/shiploop shiploop.fun
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add anshss/shiploop
Claude Code
/plugin install shiploop

Made for: Claude Code.

Or install shiploop, the plugin that ships this one along with the rest of its 2 skills, 7 commands, 3 agents.

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.

agentmods badge for update

README.md
[![agentmods](https://agentmods.dev/badge/commands/anshss/shiploop/update/github.svg)](https://agentmods.dev/commands/anshss/shiploop/update)
Your own site
<a href="https://agentmods.dev/commands/anshss/shiploop/update"><img src="https://agentmods.dev/badge/commands/anshss/shiploop/update/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.

agentmods 80×15 button for update

Your own site · 80×15
<a href="https://agentmods.dev/commands/anshss/shiploop/update"><img src="https://agentmods.dev/badge/commands/anshss/shiploop/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,992 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03992
Opus 5.5 $0.00000 $0.01597
Sonnet 5.5 $0.00000 $0.00798
Haiku 4.5 $0.00000 $0.00399

Measured 1mo ago against content hash 7ec8f579e378, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

commands/update.md · 285 lines

How it starts

The opening of the file, as written. The whole thing — 285 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

  1. Locate the hub (same priority as /setup, see "Locate the plugin" there).
  2. Verify preconditions — meta-repo workspace, harness paths not dirty, no governor running.
  3. Cheap version + diff check (writes nothing).
  4. Component-by-component bump via scaffold.sh --component <name> --yes — PRESERVES scripts/lib/workspace.sh (never overwritten without explicit ask).
  5. 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.
  6. Update .harness-version stamp (scaffold does this every run).
  7. Report a concise per-component in-sync | bumped | skipped summary.

Phase 0 — Locate the hub

Resolve HUB in priority order:

  1. ${CLAUDE_PLUGIN_ROOT} (plugin run)
  2. ${GOVERN_UPSTREAM_HARNESS_DIR} from scripts/lib/workspace.sh (operator's local fork clone)
  3. ~/.claude/skills/shiploop/ (legacy clone-into-skills)
  4. 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 · 285 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. 1mo ago Changed · +1 lines 7ec8f579e378
  2. 1mo ago Changed · -5 lines b6bbe44c3b81
  3. 1mo ago Changed 23ff4cfec79b
  4. 1mo 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 (9 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,992 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-08-31.

Claude CodeGit and workflow
Related

Other commands, from other repositories

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

pr

Handle the full workflow from current branch state to an open, CI-monitored pull request.

opsmill/infrahub-mcp · 18 tokens

codex-review

Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.

oalders/kitchen-sink · 41 tokens