An update-management procedure for the woltspace platform, including checks for published versions, compatibility, and possible breakage. It asks for explicit consent before installing an update.

Use it to inspect available platform updates, explain their impact, check the runtime environment, and install approved updates.

It reduces the chance of breaking a running installation by updating only part of a package set or restarting without approval.

update — Skill for Claude Code by jerpint/woltspace

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 jerpint/woltspace --skill update

Clone the repo

git clone --depth 1 https://github.com/jerpint/woltspace

Made for: Claude Code.

Or install woltspace, the plugin that ships this one along with the rest of its 23 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jerpint/woltspace/update/github.svg)](https://agentmods.dev/skills/jerpint/woltspace/update)

Your own site

<a href="https://agentmods.dev/skills/jerpint/woltspace/update"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jerpint/woltspace/update"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 746 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.

Model	Per session	Once invoked
Fable 5.1	$0.00036	$0.00746
Opus 5.5	$0.00014	$0.00298
Sonnet 5.5	$0.00007	$0.00149
Haiku 4.5	$0.00004	$0.00075

Measured 7d ago against content hash 628aac1a00b0, 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 7d 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.

container/skills/update/SKILL.md · 44 lines

How it starts

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

Update Woltspace

Use woltspace update as the thin, uv-backed mechanical wrapper. This workflow updates the Python package only; the separate npm @woltspace/tui is outside its scope. See manual update instructions.

Review and authorize

You are the owner's default upgrade route. Check the installed release and the one you would choose, read its notes and migration guide, take a backup fit for the change (woltspace backup), get the owner's consent, run only the approved native or host steps, then verify health.

Start with woltspace update --check. It stays on the installed X.Y line; a newer_line in its output is a migration, installed only with an exact --version after its migration guide is read and the owner agrees. A container lodge's rebuild keeps the same rule and asks for --version when the installed release is unknown. Review the target's PyPI availability/withdrawal state, all crossed GitHub release notes (vVERSION) and migrations under container/migrations/ at the reviewed release commit. Never infer migration absence from a patch version or downgrade: installing older code cannot reverse migrations. If context cannot be verified, report the gap.

A check is not installation consent. Summarize the chosen version, breaking behavior, migration actions and downtime. Obtain approval unless applicable standing permission already covers it. New incompatible requirements need human input.

Upgrade from the session

Ensure the command addresses the installed native CLI and same lodge environment, not a checkout or container runtime. It refuses source/pip/custom uv recipes rather than replacing them with a registry install. Containers remain a host-tooling responsibility.

Record current woltspace status --json, especially running state, connector diagnostics and session adoption. Report pre-existing degradation. A running update briefly takes the control plane, tunnel and connectors offline; tmux sessions survive. Existing sessions retain loaded instructions, while new sessions receive newly synced skills.

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

7d ago Changed · +2 lines 628aac1a00b0
26d ago Changed · +2 lines 0a0a189e1316
1mo ago Changed · -57 lines 4c523e527891
1mo ago Changed · -1 lines 56b9d5a49fd2
1mo ago Changed · -107 lines · -3 tokens per session scan C → A 502993f73ad2
2mo ago Changed · +2 lines 5ffcc870986d
2mo ago First seen · 203 lines · 39 tokens per session scan C 901eab430ec9

Subscribe to this mod's changes

update is a skill published in the GitHub repository jerpint/woltspace (22 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 746 once invoked, about $0.0001 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-09-09.

DevOps and cloud

update next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
updatejerpint/woltspace	Skill	22	today	MIT	A	36	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	3d ago	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	315k	6d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code