openrig-upgrade

openrig-upgrade is a skill for Claude Code, Codex from mvschwarz/openrig. It costs 43 tokens per session (2,662 once invoked), scanned A, original, Apache-2.0.

Instructions for upgrading the OpenRig command-line tool and background service while keeping running agent sessions alive. OpenRig separates the agent processes from the service that manages sessions, databases, transcripts, and metadata.

In plain words
What is it for?
Use it for live daemon upgrades, database or migration changes, tmux session preservation, and documenting evidence for a safe hot-upgrade procedure.
Why use it?
It prevents a service restart from accidentally killing active tmux-backed sessions and explains how to preserve continuity during an upgrade.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for live daemon upgrades, database or migration changes, tmux session preservation, and documenting evidence for a safe hot-upgrade procedure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mvschwarz/openrig/openrig-upgrade
About the project

OpenRig is a software harness that coordinates Claude Code and Codex coding agents as one system, with agent teams defined in YAML and launched together. It is for organizing persistent teams of coding agents that can delegate work to specialists and return results or decisions. The catalogue lists 53 skills and one plugin as add-ons for OpenRig.

mvschwarz/openrig · 8,192 stars · on GitHub · openrig.dev

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.

Any agent
npx skills add mvschwarz/openrig --skill openrig-upgrade
Clone the repo
git clone --depth 1 https://github.com/mvschwarz/openrig

Made for: Claude Code, Codex.

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 openrig-upgrade

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mvschwarz/openrig/openrig-upgrade"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/openrig-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,662 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00043 $0.02662
Opus 5.5 $0.00017 $0.01065
Sonnet 5.5 $0.00009 $0.00532
Haiku 4.5 $0.00004 $0.00266

Measured 2d ago against content hash 5653ccb547ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

openrig-upgrade 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.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/backup-sqlite.mjs, scripts/inspect-upgrade.mjs, scripts/migrate-telemetry-state-0.5.9.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

packages/daemon/specs/agents/shared/skills/core/openrig-upgrade/SKILL.md · 275 lines

How it starts

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

Upgrade OpenRig

An upgrade is an observed agent workflow, not a transaction hidden behind one command. Hosts differ, process state drifts, local plugin files accumulate, and the useful response to a failed step depends on what is still alive.

The agent owns the sequence. Stop after every mutation and observe the actual effect before choosing the next step. There is deliberately no end-to-end upgrade subcommand.

Safety model

Keep these planes separate:

  • Seats normally live in tmux and can survive a daemon restart.
  • The daemon, database, wrappers, and managed plugin projection are the control plane being changed.
  • rig down tears down seats. It is not part of a continuity-preserving upgrade.

Before acting, name the rigs and seats whose continuity matters. On a production host, use the host's normal operator ceremony. On a recovery-friendly build VM, the orchestrator may adopt a tested runtime directly, but still observes each step and stops on unexplained drift.

When recovery crosses an instance boundary

Before either lane changes runtime state, record one host-qualified executor and explicitly select the queue store that owns the recovery ruling. State whether the original owner continues, waits, or transfers; an open obligation in another store is not exclusive custody of this ruling. If the original store is down, retain its owner's disposition in the surviving ruling and communicate it to that owner before a competing executor acts.

A refused claim means reconcile ownership with the ruling owner before any further runtime action; it does not authorize continuing under a separate older row. A return names the full executor address and deliberately selected store. Read the resulting row there, including source, destination, body, and the original owner's disposition, before resuming. Receipt creation alone does not establish that a waiting lane received or accepted the transfer.

The loop

For every step:

  1. Inspect. Derive current facts from the live host.
  2. Decide. Choose one bounded mutation and state its expected effect.
  3. Act once. Do not bundle the next mutation with it.
  4. Observe. Check the process, listener, database, plugin, and seat surfaces that the step could have changed.
  5. Continue, adapt, or stop. A failed expectation is information for the agent, not permission for a blind retry.

Read the full file on GitHub · 275 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 Changed · +6 lines 5653ccb547ef
  2. 18d ago Changed · +2 lines 0ddbe16d8c93
  3. 1mo ago Changed · +16 lines c3555c66abe0
  4. 1mo ago Changed · +81 lines 986be9d3ede0
  5. 1mo ago Changed · -235 lines · +2 tokens per session 818538363e60
  6. 1mo ago First seen · 405 lines · 41 tokens per session scan A 797d6e4c9524

Subscribe to this mod's changes

openrig-upgrade is a skill published in the GitHub repository mvschwarz/openrig (8,192 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 2,662 once invoked, about $0.0002 per session on Opus 5.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-30.