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 rp1-run/rp1 --skill rp1-migrategit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/rp1-run/rp1/rp1-migrate)<a href="https://agentmods.dev/skills/rp1-run/rp1/rp1-migrate"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/rp1-migrate/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.
<a href="https://agentmods.dev/skills/rp1-run/rp1/rp1-migrate"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/rp1-migrate.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00515 |
| Opus 5.5 | $0.00007 | $0.00206 |
| Sonnet 5.5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
rp1-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 19d 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.
What it actually says
Migrate Legacy rp1 Artifacts
Detect and safely migrate legacy rp1 project artifacts. This command changes files and Arcade database rows, so require explicit confirmation before the mutating step.
Detect
Run:
rp1 agent-tools rp1-root-dir
Read data.needsMigration, data.migrationHint, data.isWorktree, and
data.projectRoot from the successful result. If data.isWorktree is true,
tell the user that migration targets the main repository at
data.projectRoot, and that the command must be run from there.
Stop and ask the user to rerun the skill from that main repository before
previewing or applying migration.
If the command fails because the legacy project is missing project_id, treat
that error as recoverable evidence that migration is needed. Stop only for the
no rp1 project, run rp1 init error. If detection succeeds with
needsMigration: false, report that there is nothing to migrate and stop.
Preview and Confirm
Run:
rp1 migrate --dry-run
Present the output as a partial preview: dry-run reports planned steps but does not compute exact file-move counts or stanza diffs. Recommend stopping Arcade if it is running because migration changes database rows. Ask for explicit confirmation before continuing.
Migrate and Verify
After confirmation, run rp1 migrate and show its summary. Then rerun
rp1 agent-tools rp1-root-dir.
- If
needsMigrationis false, confirm migration succeeded. - If it remains true, report the remaining reasons from
migrationHintverbatim. Skipped conflicts or unrelated entries in the legacy directory are left in place by design; point the user to the legacy path and do not rerun migration in a loop.
Do not offer --to-central; it is out of scope for this skill. Refer users to
the rp1 migrate reference documentation for that separate option.
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.
- 19d ago First seen · 69 lines · 18 tokens per session scan A e5fed7af502a
rp1-migrate is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 16d ago), licensed Apache-2.0. It adds 18 tokens to every session and 515 once invoked, about $0.0001 per session on Opus 5.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-09-27.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
database-design
Database design and optimization skill covering ER diagrams, normalization, indexing, sharding, query optimization, and database best practices. Use this skill when designing database schemas, optimizing queries, planning data architecture, or need guidance on database scaling and performance tuning.
diagram-builder
A diagram-making guide for system architectures, workflows, data flows, sequence diagrams, state machines, and database relationship diagrams. It supports inline SVG visuals and Mermaid code, which describes diagrams as text.
product-management
Expertise in product management lifecycle, from ideation to launch. Covers requirements gathering, user story creation, prioritization, and product strategy. Use this skill for product planning, writing PRDs, defining MVPs, or competitive analysis.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".