What is sails-program-evolution?

A planning guide for updating a Gear or Vara Sails smart contract after it has been deployed. It covers new contract versions, compatibility, cutover, and moving stored data from version 1 to version 2.

Use it to plan contract upgrades, interface or event changes, frontend and indexer compatibility, disabling the old contract, and state migration.

Changing a live contract can break users, frontends, or data tools if interfaces and stored data change unexpectedly. This helps plan the change and keep the old and new versions working safely during the transition.

sails-program-evolution — Skill for Claude Code and Codex by gear-foundation: A planning guide for updating a Gear or Vara…

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/gear-foundation/vara-skills/sails-program-evolution

Any agent

npx skills add gear-foundation/vara-skills --skill sails-program-evolution

Clone the repo

git clone --depth 1 https://github.com/gear-foundation/vara-skills

Made for: Claude Code, Codex.

Or install vara-skills, the plugin that ships this one along with the rest of its 26 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/gear-foundation/vara-skills/sails-program-evolution.svg)](https://agentmods.dev/skills/gear-foundation/vara-skills/sails-program-evolution)

Your own site

<a href="https://agentmods.dev/skills/gear-foundation/vara-skills/sails-program-evolution"><img src="https://agentmods.dev/badge/skills/gear-foundation/vara-skills/sails-program-evolution.svg" alt="Measured on agentmods" height="20"></a>

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

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

Model	Per session	Once invoked
Fable 5	$0.00071	$0.00755
Opus 5	$0.00036	$0.00378
Sonnet 5	$0.00014	$0.00151
Haiku 4.5	$0.00007	$0.00076

Measured 5d ago against content hash b7a0cd3af406, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sails-program-evolution 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 5d 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/sails-program-evolution/SKILL.md · 63 lines

How it starts

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

Sails Program Evolution

Overview

Plan how a released Sails contract evolves after deployment.

Use this skill when the work is no longer just “implement a feature”, but instead requires thinking about versioning, compatibility, cutover, ReadOnly handling, frontend/indexer impact, or migration from V1 to V2.

Start Here

Read ../../references/contract-interface-evolution.md, ../../references/gear-sails-production-patterns.md, ../../references/sails-idl-client-pipeline.md, ../../references/sails-program-and-service-architecture.md, and ../../references/sails-header-wire-format.md.

Use ../../assets/architecture-template.md for the architecture note and ../../assets/task-plan-template.md for the ordered task plan.

Write outputs to:

docs/plans/YYYY-MM-DD-<topic>-architecture.md
docs/plans/YYYY-MM-DD-<topic>-tasks.md

Route Here When

a released contract must gain a new deployed version
public routes, replies, or events may change
frontend or indexer compatibility must be preserved during cutover
the old contract may need ReadOnly or write-disable behavior
a future migration path must be designed even if migration is not implemented now
state migration from V1 to V2 is part of scope

Working Model

Classify the change first: additive, breaking, migration-readiness only, or migration now.
Treat Gear/Sails evolution as V1 -> V2 -> cutover, not as hot-swapping live contract code in place.
Keep public routes, reply shapes, and emitted events stable unless the architecture explicitly versions them.
Make contract version, status, and cutover behavior explicit.
If migration is required, split responsibilities across V1, V2, and the off-chain migrator.
Record frontend, generated-client, and indexer implications before implementation begins.
Route implementation to ../sails-architecture/SKILL.md, ../task-decomposer/SKILL.md, ../sails-rust-implementer/SKILL.md, ../sails-idl-client/SKILL.md, and ../sails-local-smoke/SKILL.md as needed.

Read the full file on GitHub · 63 lines

Files

What ships with it

3 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.

5d ago First seen · 63 lines · 71 tokens per session scan A b7a0cd3af406

Subscribe to this mod's changes

sails-program-evolution is a skill published in the GitHub repository gear-foundation/vara-skills (17 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 755 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-30.

Planning Web3 and blockchain

official-sui-skills

Pointer to the official Mysten Labs skills for building on Sui — language fundamentals, object model, PTBs, SDKs, publishing, upgrades, frontend integration, accessing on-chain data. Maintained upstream at github.com/MystenLabs/skills; pinned to the same ref the audit catalog derives from (see…

MystenLabs/sui · 116 tokens

nip85-trusted-assertions

The NIP-85 trusted-assertions model in Quartz (nip85TrustedAssertions/) — kind 10040 trust-provider lists, kind 30382 contact cards / user assertions, 30383 event assertions, 30384 addressable assertions, 30385 external-id assertions. Use when building or parsing these events, working with the typed tags (RankTag…

vitorpamplona/amethyst · 148 tokens

sails-program-evolution