migrate

A migration tool that converts older Sigint configuration files into the newer JSON format and creates a project context file.

In plain words
What is it for?
Use it to migrate project or global Sigint settings, including configurations written as markdown or older version 1 JSON.
Why use it?
It avoids rewriting old configuration by hand and keeps the original files backed up. It can also preview changes before making them.

Skill for Claude CodeCodex

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

Made for: Claude Code, Codex.

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,498 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 $0.00070 $0.02498
Opus 5 $0.00035 $0.01249
Sonnet 5 $0.00014 $0.00500
Haiku 4.5 $0.00007 $0.00250

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

Security

Grade A, and why

migrate 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 2d 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/migrate/SKILL.md · 301 lines

How it starts

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

Sigint Migrate Skill

Migrates legacy sigint configuration to the v2.0 JSON format with per-topic support. Safe to run multiple times (idempotent). Always backs up source files before overwriting.

Structured Data Protocol: JSON file creation MUST follow protocols/STRUCTURED-DATA.md. Use jq via Bash for writing sigint.config.json. Every write MUST be followed by schema validation using schemas/sigint-config.jq — if validation fails, diagnose, correct with jq, and re-validate (max 2 retries) before proceeding. See the Retry-and-Correct protocol in protocols/STRUCTURED-DATA.md.

Arguments

Parse $ARGUMENTS:

  • --dry-rundry_run = true — preview what would be written, no files modified
  • --globalmigrate_global = true — also migrate ~/.claude/sigint.local.md (default: project only)

Phase 0: Detect Source Files

Step 0.1: Inventory legacy config files

Check for each (silent, no errors if missing):

  • project_local_md./.claude/sigint.local.md exists
  • global_local_md~/.claude/sigint.local.md exists (relevant only if migrate_global)
  • project_config_v1./.sigint.config.json exists and its version field is "1.0" (if version is missing or not "1.0", ignore this file and emit: "Skipping .sigint.config.json — version is not 1.0.")
  • target_exists./sigint.config.json exists

Step 0.2: Check for existing v2.0 target

If ./sigint.config.json exists:

  • Parse it. If version == "2.0":
    AskUserQuestion(
      question: "sigint.config.json v2.0 already exists. How would you like to proceed?",
      options: [
        "Merge: add missing topics from legacy config, preserve existing topic customizations",
        "Overwrite: replace entirely with freshly migrated config",
        "Cancel"
      ]
    )
    
    Store as merge_mode ("merge", "overwrite", or cancel/exit).
  • If version != "2.0": treat as overwrite.

Step 0.3: Early exit if nothing to migrate

If no source files found AND no v1.0 target:

  • Output: "Nothing to migrate. No legacy config files found."
  • Output: "To create a fresh config, run /sigint:init."
  • Exit.

Read the full file on GitHub · 301 lines

Files

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.

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. 2d ago First seen · 301 lines · 70 tokens per session scan A 2a1e23c521ca

Subscribe to this mod's changes

migrate is a skill published in the GitHub repository zircote-plugins/sigint (20 stars, last pushed 15d ago), licensed MIT. It adds 70 tokens to every session and 2,498 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.

Related

Other skills, from other repositories

gr-competitor

竞品深度扫描。批量抓取对手落地页(title/h1/intro/pricing)、定价页、博客 top 10、 变更历史(Wayback)。底层调 actionbook(并发 30 tab + 省 90% token)。 当用户说"分析对手"、"看看竞品在做啥"、"找对标"、"扫一下 top 10"时调用。.

Gingiris-1031/gingiris-skills · 99 tokens

startup-design

Design, validate, and plan a startup from scratch. Covers market research, competitive analysis, business model, brand identity, product definition, financial projections, and validation experiments. Trigger when the user has a startup idea to explore, wants to validate a business concept, needs a business plan or…

ferdinandobons/startup-skill · 108 tokens

startup-pitch

Build investor-ready pitch scripts in multiple formats (10-min, 5-min, 2-min, 1-min elevator, investor email). Produces pitch narratives, Q&A preparation, pitch scoring rubric, and optional investor roleplay practice. Use when the user wants to create a pitch, prepare for investor meetings, craft a startup pitch…

ferdinandobons/startup-skill · 186 tokens

startup-competitors

Deep competitive intelligence for any market. Analyzes competitors' products, pricing, customer sentiment, GTM strategy, and growth signals using real web data. Produces battle cards, pricing landscape, and feature matrix. Use when the user wants to understand their competitive landscape, analyze competitors, compare…

ferdinandobons/startup-skill · 155 tokens

startup-positioning

Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or…

ferdinandobons/startup-skill · 186 tokens

mapping-markets

Map the market around any company from its domain alone — competitors, substitutes, the infrastructure it sits on, the directories that list it, the publications that cover it and the communities its buyers argue in — with a source and a reason on every entry. Use this skill whenever someone wants a competitive…

mo-root/open-kb · 134 tokens