update

update is a command for Claude Code from paulonasc/orchestra. It costs 0 tokens per session (957 once invoked), scanned C, original, MIT.

A maintenance command for Orchestra, a software toolkit that can be installed from its Git repository or copied into a project. It can update the installation, show local usage statistics, or handle release-related maintenance.

In plain words
What is it for?
Upgrading Orchestra, synchronizing its files with the project, displaying local usage analytics, and carrying out release maintenance.
Why use it?
It puts routine upgrade and maintenance actions in one command and can restore the previous installation if an update fails.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions subagents; names the AskUserQuestion tool.

Good fit Upgrading Orchestra, synchronizing its files with the project, displaying local usage analytics, and carrying out release maintenance.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/paulonasc/orchestra/update
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.

Clone the repo
git clone --depth 1 https://github.com/paulonasc/orchestra

Made for: Claude Code.

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/paulonasc/orchestra/update/github.svg)](https://agentmods.dev/commands/paulonasc/orchestra/update)
Your own site
<a href="https://agentmods.dev/commands/paulonasc/orchestra/update"><img src="https://agentmods.dev/badge/commands/paulonasc/orchestra/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/paulonasc/orchestra/update"><img src="https://agentmods.dev/badge/commands/paulonasc/orchestra/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 957 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00957
Opus 5.5 $0.00000 $0.00383
Sonnet 5.5 $0.00000 $0.00191
Haiku 4.5 $0.00000 $0.00096

Measured 1mo ago against content hash fb8943e5340b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

update scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$_OLD/.git" # keep it vendored
commands/update.md · 92 lines

How it starts

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

/o update / stats / release — Maintenance

/o update — Upgrade Orchestra

Step 1 — Save old version:

_OLD_VER=$(cat __ORCHESTRA_DIR__/VERSION 2>/dev/null | tr -d '[:space:]')

Step 2 — Detect install type and update:

_ORCH_ROOT=$(grep "^root:" .orchestra.link 2>/dev/null | sed 's/^root: *//')

Check install type:

[ -d "__ORCHESTRA_DIR__/.git" ] && echo "git install" || echo "vendored install"

If git install — pull and sync (existing flow):

cd __ORCHESTRA_DIR__ && git pull origin main && ./setup sync "$_ORCH_ROOT"

If vendored install — clone, swap, and sync:

_TMP=$(mktemp -d)
git clone --depth 1 https://github.com/paulonasc/orchestra.git "$_TMP/orchestra"
_OLD="__ORCHESTRA_DIR__"
cp "$_OLD/VERSION" "$HOME/.orchestra-state/just-upgraded-from" 2>/dev/null
mv "$_OLD" "${_OLD}.bak"
mv "$_TMP/orchestra" "$_OLD"
rm -rf "$_OLD/.git"  # keep it vendored
cd "$_OLD" && ./setup sync "$_ORCH_ROOT"
if [ $? -eq 0 ]; then
  rm -rf "${_OLD}.bak" "$_TMP"
else
  # Rollback on failure
  rm -rf "$_OLD"
  mv "${_OLD}.bak" "$_OLD"
  rm -rf "$_TMP"
fi

Step 3 — Show changelog:

_NEW_VER=$(cat __ORCHESTRA_DIR__/VERSION 2>/dev/null | tr -d '[:space:]')
__ORCHESTRA_DIR__/bin/orchestra-changelog "$_OLD_VER" "$_NEW_VER" 2>/dev/null

If the changelog script returns content, present it to the user as "What's new in Orchestra." Format the output nicely — show features, then prompt for any actions listed in the changelog.

Changelog actions use a simple format in changelog .md files:

  • action: relink — run the command automatically (it's a sync/relink, safe to auto-run since setup sync just ran above)
  • action: suggest — show the prompt to the user and ask if they want to try it. Don't auto-run.

If no changelog output (same version or no entries), just report: "Orchestra is up to date (v{version})."

Step 4 — Enable heartbeat (automatic):

After update completes, check if heartbeat is scheduled (look for heartbeat_scheduled: true in state/sessions/{session-id}.md). If not, run /o heartbeat to set it up. Remember: cron scheduling happens in the main agent (3 tool calls: CronList → CronDelete all → CronCreate with inline prompt). Never delegate cron creation to a subagent.

Read the full file on GitHub · 92 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 First seen · 92 lines · 0 tokens per session scan C fb8943e5340b

Subscribe to this mod's changes

update is a command published in the GitHub repository paulonasc/orchestra (15 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 957 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.