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.
npx agentmods add skills/kaininx/plaintab/storage-migrationnpx skills add kaininx/PlainTab --skill storage-migrationgit clone --depth 1 https://github.com/kaininx/PlainTabWrote 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.
[](https://agentmods.dev/skills/kaininx/plaintab/storage-migration)<a href="https://agentmods.dev/skills/kaininx/plaintab/storage-migration"><img src="https://agentmods.dev/badge/skills/kaininx/plaintab/storage-migration.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00063 | $0.00663 |
| Opus 5 | $0.00032 | $0.00331 |
| Sonnet 5 | $0.00013 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
storage-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PlainTab Storage Migration
Use this skill as a red-line checklist for storage changes. User data safety and jump-upgrade behavior matter more than implementation neatness.
First Reads
- Read
.claude/rules/00-core.md. - Read
.claude/rules/10-storage.md. - If wallpaper rendering, first paint, settings UI, language, search, or command palette storage is touched, read the matching rule file from
.claude/rules/README.md.
Version Rules
DB_VERSIONis only for IndexedDB structure: object stores, indexes, keyPath, or autoIncrement.LS_VERSION/ptab_schema_versionis for PlainTab application data semantics.- If an IndexedDB-only change affects key names, record shape, references, old data cleanup, or jump upgrades, bump
LS_VERSIONand add aWallpaperData.migrate()path. - Do not use IndexedDB version upgrades for application-level migration decisions.
- Pure discardable cache changes do not need
LS_VERSIONif missing or stale cache cannot be misread and does not require cleanup.
Migration Discipline
Before production edits, write or update a focused check in docs/ai-tasks/ and watch it fail for the missing migration behavior.
For each migration step:
- Detect from persisted data, not app release numbers. Prefer
ptab_schema_version, legacyptab_version, old key presence, and current model facts. - Make the step idempotent. A browser close midway must be safe to retry.
- Write large data first, then write references.
- Never write references to missing Blob records.
- Remove references before deleting large data.
- Mark migration complete only after required new data and cleanup succeed.
- Do not overwrite non-default data already created by a newer version.
- Keep runtime modules reading only the current schema after migration.
Cleanup Rules
- Delete obsolete localStorage keys after successful migration.
- Delete obsolete IndexedDB keys with targeted deletes. Do not delete the whole
PlainTabdatabase while current data uses the same store. - Avoid permanent top-level marker keys for one-off migrations. If cleanup truly needs an idempotent retry marker, keep it scoped to an existing owned model, document why persisted facts are insufficient, and include a cleanup/removal path.
- Keep old migration code for enough releases to support users who skip versions.
What ships with it
1 file 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.
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.
- 4d ago First seen · 57 lines · 63 tokens per session scan A edc28c19d9fb
storage-migration is a skill published in the GitHub repository kaininx/PlainTab (88 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 663 once invoked, about $0.0003 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.
Other skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
moderator-page-migration
Port a moderator page from the main Next.js app (src/pages/moderator/) into apps/moderator. Use when asked to migrate, move or cut over a /moderator/ page to the spoke, or to port its tRPC procedures and Prisma services to SvelteKit loads/actions and Kysely.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
sql-translate
Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.).