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 skills add nirecom/agents --skill migrate-repogit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/migrate-repo)<a href="https://agentmods.dev/skills/nirecom/agents/migrate-repo"><img src="https://agentmods.dev/badge/skills/nirecom/agents/migrate-repo.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.1 | $0.00027 | $0.01339 |
| Opus 5 | $0.00014 | $0.00669 |
| Sonnet 5 | $0.00005 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
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 7d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Always run --dry-run first.
Irreversibility hard rule
gh issue createconsumes monotonically increasing global issue numbers; they can never be reused, freed, or reassigned. Every canary stage is irreversible.- Each stage MUST run as its own process: never chain stages, never pipe
yesinto the orchestrator, never run two stages in one command. AskUserQuestionis the only gate between stages — never invokeorchestrate.shinside a pipeline that supplies stdin.
Pre-flight
gh auth status— confirmprojectscope is active.AGENTS_CONFIG_DIRmust be set.- Step 1 label setup is delegated to
bin/github-issues/bootstrap-labels.sh.
Procedure
MR-1. Get the migration target path from the user.
- Never infer
REPO_PATHfrom a path mentioned only as documentation / reference / context — accept only the path the user explicitly designates as the target. - Resolve
REPO_PATHto an absolute path, then AskUserQuestion: "Migration target =<abs path>— correct? (confirm this is NOT the agents repo itself)"- "Yes, proceed with this path" → MR-2
- "No, re-enter the correct path" → re-collect
REPO_PATH, repeat MR-1
MR-2. Preview + capture the snapshot.
- Run:
eval "$(bash "$AGENTS_CONFIG_DIR/skills/migrate-repo/scripts/preview-and-capture.sh" "$REPO_PATH")"— runs the dry-run, mirrors it to stderr, and exportsMIGRATE_ACK_UP_TO_ISSUE_N+MIGRATE_ACK_SELF_COUNT_AT_ACK. - Inspect
MIGRATE_SELF_REPO_DETECTED:=1→ AskUserQuestion: "WARNING: target (<REPO_PATH>) is the agents repo itself. Proceed ONLY for an intentional agents-repo Phase 3 self-migration."- "Proceed as agents-repo Phase 3" → MR-3
- "Abort and fix the path" → stop the skill
=0→ MR-3
MR-3. Dry-run review gate. AskUserQuestion: "Dry-run reviewed — proceed to History canary 1, or abort?"
- Note in the question: if an existing-issues WARNING was shown, migrated issues permanently lose the "early issue numbers = history chronology" invariant.
- "proceed" → MR-4
- "abort" → stop the skill (no irreversible mutation yet)
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.
- 7d ago First seen · 78 lines · 27 tokens per session scan A f8e4a20742fb
migrate-repo is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,339 once invoked, about $0.0001 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.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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.
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…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…