openclaw-upgrade

openclaw-upgrade is a skill for Claude Code, Codex from KCNyu/clawock. It costs 110 tokens per session (1,469 once invoked), scanned A, original, MIT.

A cautious procedure for upgrading OpenClaw, an agent system that may run scheduled jobs and other live services. It checks the target version, known issues, active scheduled jobs, local patches, and the system after the update.

In plain words
What is it for?
Use it when checking for or installing a newer OpenClaw version. It is intended for systems where scheduled jobs must keep running safely during maintenance.
Why use it?
It reduces the risk that an upgrade interrupts a running job, loses scheduled tasks, breaks embeddings, or leaves local changes unapplied.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: mentions Codex; built for openclaw.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash ops/host/reapply_openclaw_patches.sh.

Good fit Use it when checking for or installing a newer OpenClaw version. It is intended for systems where scheduled jobs must keep running safely during maintenance.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/KCNyu/clawock
agentmods
npx agentmods add skills/kcnyu/clawock/openclaw-upgrade

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kcnyu/clawock/openclaw-upgrade"><img src="https://agentmods.dev/badge/skills/kcnyu/clawock/openclaw-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,469 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 92
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00110 $0.01469
Opus 5 $0.00055 $0.00734
Sonnet 5 $0.00022 $0.00294
Haiku 4.5 $0.00011 $0.00147

Measured 9d ago against content hash 7afa8ca30775, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

openclaw-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 9d 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.

skills/openclaw-upgrade/SKILL.md · 97 lines

How it starts

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

OpenClaw Safe Upgrade

Kcn runs a live automated trading system on OpenClaw. An upgrade that loses crons, breaks embeddings, or orphans an in-flight cron is a production incident. This is the battle-tested flow (5.28→6.1→6.5→6.6→6.8). Full version-specific history lives in auto-memory openclaw-update-missing-deps.md — read it first for the target version's known traps.

0. Check + decide

  1. openclaw --version vs npm view openclaw version (latest). Pull the changelog (npm pack openclaw@<v>package/CHANGELOG.md) and judge relevance — don't upgrade reflexively.
  2. Read auto-memory openclaw-update-missing-deps.md for that version's traps.

1. 🔴 Never restart the gateway while a cron is in-flight

Use the structured runtime field, not a text grep:

openclaw cron list --json \
  | jq -e '[.jobs[] | select(.state.runningAtMs != null)] | length == 0'

If this is not true, wait. A SIGTERM mid-run can orphan the cron into permanent running. Use --no-restart and pick a quiet window between slots (bash ops/host/check_crons.sh --timeline).

2. Update (built-in updater, since 6.x)

openclaw update --tag <version> --no-restart --yes

This auto-reinstalls/links managed plugins (weixin, llama-cpp, codex) — no manual pnpm add, no systemd edits, no restore-llama-embeddings.sh needed. (Pre-6.x manual flow is in the memory file.)

3. 🔴 Reapply all upgrade-sensitive local patches before restart

The updater replaces the installed dist/ tree. From the live workspace run:

bash ops/host/reapply_openclaw_patches.sh

The wrapper applies these idempotent host scripts in order:

  1. /root/tools/openclaw/current/patch-embedding-threads1.sh
  2. /root/tools/openclaw/current/patch-memory-search-timeout.sh
  3. /root/tools/openclaw/current/patch-minimax-m3-priority.sh
  4. /root/tools/openclaw/current/patch-minimax-response-header-timeout.sh

It then verifies all four markers, runs node --check on every modified bundle, and compiles the maintenance detector. It does not restart the gateway.

Read the full file on GitHub · 97 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. 9d ago First seen · 97 lines · 110 tokens per session scan A 7afa8ca30775

Subscribe to this mod's changes

openclaw-upgrade is a skill published in the GitHub repository KCNyu/clawock (14 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 1,469 once invoked, about $0.0006 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-30.