save-data-schema-migration

save-data-schema-migration is a skill for Codex from hoatv2211/GameStudio-CodexKIT. It costs 36 tokens per session (741 once invoked), scanned A, original, MIT.

A safety-focused process for upgrading saved player data from one recognized format version to another while preserving the original data.

In plain words
What is it for?
Use it for save-field renames, added defaults, removed fields, import upgrades, and compatibility checks between save versions.
Why use it?
It reduces the risk of losing player progress and blocks migrations when the version chain, backup, rollback plan, or approval is missing.

Skill for Codex

Written for Codex: agents/openai.yaml present.

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.

agentmods
npx agentmods add skills/hoatv2211/gamestudio-codexkit/save-data-schema-migration
Any agent
npx skills add hoatv2211/GameStudio-CodexKIT --skill save-data-schema-migration
Clone the repo
git clone --depth 1 https://github.com/hoatv2211/GameStudio-CodexKIT

Made for: 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 save-data-schema-migration

README.md
[![agentmods](https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/save-data-schema-migration.svg)](https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/save-data-schema-migration)
Your own site
<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/save-data-schema-migration"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/save-data-schema-migration.svg" alt="Measured on agentmods" 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 741 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00036 $0.00741
Opus 5 $0.00018 $0.00370
Sonnet 5 $0.00007 $0.00148
Haiku 4.5 $0.00004 $0.00074

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

Security

Grade A, and why

save-data-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 6d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/save_migration.py), 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.

skills/save-data-schema-migration/SKILL.md · 79 lines

How it starts

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

Save Data Schema Migration

Overview

Plan and test player-save migrations through an explicit version chain while preserving the original payload and refusing unknown or newer versions.

When to use

Use for save field renames, defaults, removals, version upgrades, backward compatibility, import migrations, or player-data format changes.

When NOT to use

Do not use for database schema migration, arbitrary config edits, or direct production player-save rewrites without a project runbook.

Required inputs and context discovery

Require current and target versions, migration chain, save authority, fixture set, backup scope, rollback method, compatibility window, reviewer, human approval, privacy constraints, and validation checks.

Safety and risk level

High-risk. Unknown versions, incomplete chains, missing backup, missing rollback, missing reviewer, live player data, or missing approval means BLOCKED.

Workflow

  1. Identify save authority, current version, target version, and supported compatibility range. Completion criterion: unknown or newer versions are BLOCKED.
  2. Review each one-version migration step for rename, default, removal, and data loss. Completion criterion: irreversible transformations are explicit.
  3. Preserve the original fixture and run migration on a copy. Completion criterion: fixture mutation cannot destroy rollback input.
  4. Validate migrated semantics and backward/forward compatibility expectations. Completion criterion: expected fields and values are asserted.
  5. Prepare exact backup, apply, rollback, reviewer, and approval evidence for real scope. Completion criterion: real player data remains untouched until authorized.

Evidence and output contract

Produce save-migration-plan.json with versions, migration hashes, fixture results, compatibility, rollback, reviewer, approval, verdict, and limitations.

Handoff contract

Record save authority, version chain, fixture paths, migration result, data-loss risks, backup/rollback, approval state, and next authorized action.

Read the full file on GitHub · 79 lines

Files

What ships with it

2 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. 6d ago First seen · 79 lines · 36 tokens per session scan A 7be862f3883d

Subscribe to this mod's changes

save-data-schema-migration is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 741 once invoked, about $0.0002 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

embeddings

Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.

ruvnet/ruflo · 62 tokens

moai-domain-database

Database specialist covering PostgreSQL, MongoDB, Redis, Oracle, and cloud database platforms (Neon, Supabase, Firestore). Use for schema design, query optimization, indexing strategies, data modeling, or cloud database selection. Cloud vendor guide absorbed from moai-platform-database-cloud.

modu-ai/moai-adk · 64 tokens

chroma-integration

Chroma local vector database setup and operations for development and production.

a5c-ai/babysitter · 17 tokens

milvus-integration

Milvus distributed vector database configuration for large-scale RAG applications.

a5c-ai/babysitter · 17 tokens

moai-platform-database-cloud

Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.

modu-ai/moai-adk · 51 tokens

AgentDB Performance Optimization

Optimize AgentDB performance with quantization (4-32x memory reduction), HNSW indexing (150x faster search), caching, and batch operations. Use when optimizing memory usage, improving search speed, or scaling to millions of vectors.

ruvnet/ruflo · 53 tokens