What is migrate-repo?

A migration tool for moving a repository's existing open issues into an organised framework of epics, tasks, ad-hoc work, and closed items.

It is for reviewing open issues, closing work that is already finished, grouping related issues into projects, and placing remaining work under the appropriate backlog categories.

It turns an accumulated issue backlog into a clearer roadmap, while allowing the work to be resumed and approved in batches.

migrate-repo — Skill for Claude Code by vergil-project

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.

Any agent

npx skills add vergil-project/vergil-claude-plugin --skill migrate-repo

Clone the repo

git clone --depth 1 https://github.com/vergil-project/vergil-claude-plugin

Made for: Claude Code.

Or install vergil, the plugin that ships this one along with the rest of its 15 skills, 1 agent, 2 hooks.

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/vergil-project/vergil-claude-plugin/migrate-repo/github.svg)](https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/migrate-repo)

Your own site

<a href="https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/migrate-repo"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/migrate-repo/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vergil-project/vergil-claude-plugin/migrate-repo"><img src="https://agentmods.dev/badge/skills/vergil-project/vergil-claude-plugin/migrate-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,026 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00130	$0.02026
Opus 5	$0.00065	$0.01013
Sonnet 5	$0.00026	$0.00405
Haiku 4.5	$0.00013	$0.00203

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

Security

Grade A, and why

migrate-repo 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 11d 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-repo/SKILL.md · 145 lines

How it starts

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

Migrate repo

Overview

Bring one repo's pre-framework backlog into the epic/task model at middle ambition: close what's already done, drop clear ad-hoc work under the repo's ad-hoc epic in the org .github, and reconstruct a finite epic only where a cluster of related open issues obviously forms an in-flight project. The skill is resumable (re-running only touches the not-yet-migrated remainder) and batch-approved (you approve dispositions in groups, never one issue at a time — essential for large repos). Run it per repo; it is the same procedure for every repo and every org.

When to use

"migrate <repo>", "bring <repo> into the framework", "onboard the backlog", "do the migration for <repo>". Run on one repo at a time.

Preflight

Confirm you are the USER agent (vrg-whoami --mode is user) — this skill closes issues, which only the user agent may do.
Confirm the target <owner>/<repo> and its resolved epic home — <owner>/.github for a public repo, the repo itself when private (epics.resolve_epic_home, epic #130; the epic/ad-hoc commands take --repo and echo the home). See convention #40 §3.2.

Workflow

1. Setup

Seed the canonical labels: vrg-ensure-label sync <owner>/<repo>.
Ensure the repo's ad-hoc epic exists in its resolved home: vrg-adhoc-epic ensure --repo <owner>/<repo> — it finds or creates Epic (ad hoc): <repo> (labelled epic+ad-hoc) in the repo's resolved home (<owner>/.github for a public repo, the repo itself when private) and echoes it. Record its number; ad-hoc tasks link under it.

2. Collect (resumable)

List the repo's open issues (vrg-gh issue list --repo <owner>/<repo> --state open --limit 500 --json number,title,labels,body,createdAt). Skip any already in the model: epic-labelled, already carrying a Parent: <owner>/.github#<N> line or a native sub-issue parent, or already triage-labelled. Report how many remain to classify.

3. Pass 1 — done detection

Read the full file on GitHub · 145 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.

11d ago First seen · 145 lines · 130 tokens per session scan A 4f4b8e69b55c

Subscribe to this mod's changes

migrate-repo is a skill published in the GitHub repository vergil-project/vergil-claude-plugin (2 stars, last pushed 9d ago), licensed MIT. It adds 130 tokens to every session and 2,026 once invoked, about $0.0006 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.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

migrate-repo