migrate

migrate is a skill for Claude Code from cryndoc/polisade-orchestrator. It costs 11 tokens per session (2,007 once invoked), scanned A, original, Apache-2.0.

A migration command that updates Polisade project state files to the current schema. A schema is the expected structure and set of fields in a data file.

In plain words
What is it for?
Use it when upgrading an older Polisade project. It updates project and knowledge files, adds testing information, sets a version, and can prepare version-control configuration files when needed.
Why use it?
It adds missing fields and metadata so older projects can work with the current version. It can first show the proposed changes and then apply them after confirmation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Codex.

Part of the polisade plugin — 27 skills, 2 commands shipped together

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/cryndoc/polisade-orchestrator/migrate
Any agent
npx skills add cryndoc/polisade-orchestrator --skill migrate
Clone the repo
git clone --depth 1 https://github.com/cryndoc/polisade-orchestrator

Made for: Claude Code.

Or install polisade, the plugin that ships this one along with the rest of its 27 skills, 2 commands.

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 migrate

README.md
[![agentmods](https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/migrate.svg)](https://agentmods.dev/skills/cryndoc/polisade-orchestrator/migrate)
Your own site
<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/migrate"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/migrate.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,007 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00011 $0.02007
Opus 5 $0.00005 $0.01004
Sonnet 5 $0.00002 $0.00401
Haiku 4.5 $0.00001 $0.00201

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

Security

Grade A, and why

migrate scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Самодельный Python/curl в Bitbucket/GitHub REST API утекает токены из
skills/migrate/SKILL.md · 172 lines

How it starts

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

/polisade:migrate — Schema Migration

Обновляет PROJECT_STATE.json и knowledge.json до текущей версии схемы. Добавляет недостающие поля, создаёт artifactIndex, устанавливает schemaVersion. Также добавляет testing.strategy в knowledge.json если отсутствует.

VCS bootstrap: если settings.vcsProvider отсутствует — добавляет "github". Если PM вручную переключил провайдер на bitbucket-server — создаёт .env.example (reference) и .env (stub для заполнения токенов) из plugin templates, добавляет некомментированную .env в .gitignore. Заполненный .env не перезаписывается (идемпотентность). ⚠️ Под GigaCode Filesystem Guard сам скрипт миграции может не запуститься (install-dir read-protected, #127) — тогда .env/.env.example автоматически не появятся; PM создаёт .env вручную из .env.example (cp .env.example .env) и заполняет токены (#131).

Использование

/polisade:migrate            # Dry-run — показать что изменится
/polisade:migrate --apply    # Показать diff и применить после подтверждения

Алгоритм

  1. Определить корень проекта.
  2. Запустить миграцию в режиме dry-run:
python3 {plugin_root}/scripts/polisade_migrate.py {project_root}
  1. Распарсить JSON-ответ, показать список миграций пользователю.
  2. Если пользователь подтверждает — применить:
python3 {plugin_root}/scripts/polisade_migrate.py {project_root} --apply --yes

Формат вывода

polisade_migrate.py всегда печатает один JSON-документ на stdout (контракт OPS-108 — json.loads(stdout) обязан проходить). PM-friendly сообщения и подтверждение интерактивного prompt'а уходят на stderr. Полная таблица контрактов — docs/config-reference.md § Script JSON output contracts.

Если схема актуальна

{
  "status": "up_to_date",
  "schemaVersion": 7,
  "polisadeVersion": "3.0.0",
  "touched_paths": [],
  "stage_paths": []
}

Если нужна миграция (dry-run)

{
  "status": "migration_needed",
  "current_schema": 3,
  "target_schema": 6,
  "migrations": [
    "Update schemaVersion: 3 → 7",
    "Add settings.debt.autoCreateTask: true (preserve legacy auto-TASK behavior)"
  ],
  "touched_paths": [".state/PROJECT_STATE.json"],
  "stage_paths": [".state/PROJECT_STATE.json"],
  "dry_run": true
}

Read the full file on GitHub · 172 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. 5d ago First seen · 172 lines · 11 tokens per session scan A cbad1b79b37d

Subscribe to this mod's changes

migrate is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,007 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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

deep-execution

Executes agent-enhanced council queries as one Workflow of parallel Claude analyst agents that each query a provider, evaluate response quality, ask follow-up questions, and return a schema-enforced analysis with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex…

hex/claude-council · 66 tokens

update-lid

Configure or reconcile a project for linked-intent development (LID). Dispatches on project state — fresh bootstrap, append directives to an existing agent-instructions file (AGENTS.md or CLAUDE.md), add missing mode marker, reconcile convention drift, or run mode transitions. Invoked as /update-lid. For fresh…

jszmajda/lid · 105 tokens

matryca-github

Apply Matryca maintainer standards for GitHub issues, pull requests, branches, reviews, merges, milestones, tags, releases, and remote comments. Use before any GitHub-facing action or artifact.

MarcoPorcellato/matryca-plumber · 47 tokens

matryca-logseq-io

Choose safe direct-file versus Local HTTP API access for Logseq. Use when changing graph reads, writes, background indexing, live Logseq integration, authentication, or JSON-RPC communication.

MarcoPorcellato/matryca-plumber · 45 tokens

sflo

Starts and manages SFLO factory runs through the configured runner. Use when the user explicitly asks to start, run, resume, list, kill, clean, or inspect an SFLO factory, including requests to build something with SFLO. Do not use when SFLO appears only in quoted text, documentation, examples, code, logs, or…

simonasrazm/simon-factory-lights-out · 74 tokens

map-codebase

Bootstrap LID in an existing (brownfield) codebase. Deep-reads every file in the declared scope, offers lens-based clustering options, generates skeleton LLDs/HLD/EARS bottom-up, then creates arrow docs and prompts the user to flesh out the skeletons. Token-intensive by design. Use when asked to map a codebase…

jszmajda/lid · 92 tokens