save-schema-migration

save-schema-migration is a skill for Claude Code from Simone-Tarantino/godot-superpowers. It costs 85 tokens per session (2,702 once invoked), scanned A, original, MIT.

A system for updating old game save files when the save format changes. Each save records its format version, and sequential migrations convert older versions into the current one.

In plain words
What is it for?
Use it before shipping a save-format change in a Godot game. It defines version-to-version migration functions, handles unknown versions, and tests fixture saves from released versions.
Why use it?
Without migrations, updates can make existing saves crash, lose data, or load incorrectly when fields are added, removed, renamed, or changed.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the godot-superpowers plugin — 33 skills, 15 agents, 4 hooks, 5 MCP servers shipped together

Good fit Use it before shipping a save-format change in a Godot game. It defines version-to-version migration functions, handles unknown versions, and tests fixture saves from released versions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/simone-tarantino/godot-superpowers/save-schema-migration
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 Simone-Tarantino/godot-superpowers --skill save-schema-migration
Clone the repo
git clone --depth 1 https://github.com/Simone-Tarantino/godot-superpowers

Made for: Claude Code.

Or install godot-superpowers, the plugin that ships this one along with the rest of its 33 skills, 15 agents, 4 hooks, 5 MCP servers.

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 save-schema-migration

README.md
[![agentmods](https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/save-schema-migration/github.svg)](https://agentmods.dev/skills/simone-tarantino/godot-superpowers/save-schema-migration)
Your own site
<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/save-schema-migration"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/save-schema-migration/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 save-schema-migration

Your own site · 80×15
<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/save-schema-migration"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/save-schema-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,702 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.00085 $0.02702
Opus 5 $0.00043 $0.01351
Sonnet 5 $0.00017 $0.00540
Haiku 4.5 $0.00009 $0.00270

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

Security

Grade A, and why

save-schema-migration 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/save-schema-migration/SKILL.md · 213 lines

How it starts

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

Save schema migration

A shipped game inherits every save format it ever published. The first time you add a field to SaveData and re-export, every existing player loads a save with the old shape and gets either: silent data loss (missing field defaults to zero), a hard crash (null.method() on a missing sub-Resource), or a corrupt run.

This skill is the contract for evolving save data without breaking existing players. Pair it with setup-save-system, which already includes a version field and a _migrate() stub — this skill fills in the migration registry and the test that proves it works.

Rules

  1. Every save Resource has a schema_version: int at the top level. Bump it whenever you add, remove, rename, or change the meaning of a field.
  2. Migrations are sequential. A v1 save migrates to v2, then v2 to v3 — never v1 → v3 directly. This keeps each migration small and independently testable.
  3. Migrations are pure functions of the loaded payload. They do not read the current scene, the autoloads, or anything else — same input → same output.
  4. Migrations never delete data without an explicit decision. Renaming a field? Move the value. Removing? Either drop silently with a comment or stash under _legacy.<field_name> if there is any chance you'll want it back.
  5. Every released version has a fixture save in test/fixtures/save/v<N>.tres. CI loads each fixture and asserts the migrated result matches the current schema's assert_valid() invariants.
  6. Unknown future version = refuse to load. A v5 save loaded by a v3 build means the player rolled back. Do not guess — show "save from a newer version, please update".

File shape

resources/save_data.gd (extended from setup-save-system)

class_name SaveData
extends Resource
## Top-level save container. One file per slot.
##
## When `SCHEMA_VERSION` bumps, register the matching migration in
## SaveMigrations._migrations and ship a fixture under test/fixtures/save/.

const SCHEMA_VERSION := 3   # bump on every breaking change

@export var schema_version: int = SCHEMA_VERSION
@export var timestamp: int = 0
@export var play_time_seconds: float = 0.0
@export var current_scene: String = ""
@export var entries: Dictionary[NodePath, Variant] = {}

# v3 added: difficulty preset (was inferred from world flags before)
@export var difficulty: StringName = &"normal"

func assert_valid() -> void:
    assert(schema_version == SCHEMA_VERSION, "save not migrated to current schema")
    assert(timestamp > 0, "missing timestamp")
    assert(difficulty in [&"easy", &"normal", &"hard"], "invalid difficulty: %s" % difficulty)

Read the full file on GitHub · 213 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 · 213 lines · 85 tokens per session scan A a635acaa4166

Subscribe to this mod's changes

save-schema-migration is a skill published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 85 tokens to every session and 2,702 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

game-build-team

Build a Godot 4 / GDScript game feature with a coordinated agent team — a Manager (you), a Creative Director, a Logic Developer, an Animation Developer, and a Tester — that iteratively and autonomously design, build, juice, and verify the feature against the project's design contract to a strict, un-skippable quality…

Varalix-Digitech-Solutions/game-build-team-skill · 248 tokens

avatar-contribution-pr

Turn an avatar GitHub issue (from the in-app avatar-editor easter egg) into a merged sprite — validate the art, then either add a new module or replace an existing one, and open a PR that closes the issue. Handles both "Avatar contribution: " (a brand-new sprite) and "Avatar edit: " (a hand-redraw of an existing…

khromov/codebay · 0 tokens

wavedash

Use when building, integrating, testing, uploading, publishing, or preparing a browser game for Wavedash, including CLI setup, Wavedash SDK features, multiplayer, achievements, leaderboards, cloud saves, player identity, user-generated content, store metadata, monetization, and content guidelines.

wvdsh/ai · 63 tokens

godot-engineer

!cat skills/shared/protocols/3d-spatial-foundations.md 2>/dev/null || true !cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/game-test-protocol.md 2>/dev/null || true…

buiphucminhtam/forgewright · 52 tokens

bootstrap-game-qa-system

Use ONCE per browser-game project to set up the game-qa infrastructure. Copies the shipped runner template, the adapter skeleton, and the journey schema; gap-fills the project's existing debug system if one is present. Skip for non-game projects.

Bulugulu/game-qa · 56 tokens

requesting-game-qa

Use ONLY for QA on browser-game feature work. Triggers when the engineer signals readiness for QA: "request QA on X", "verify X", "QA this", "ready for QA on X", "this should be ready, can we make sure it works?" Compiles a brief, drives test-plan sign-off, then hands off to game-qa. Skip for tooling, build scripts…

Bulugulu/game-qa · 93 tokens