Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/konveyor-ecosystem/playpen-pf-mig-skillsnpx agentmods add skills/konveyor-ecosystem/playpen-pf-mig-skills/code-migrationWrote 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/konveyor-ecosystem/playpen-pf-mig-skills/code-migration)<a href="https://agentmods.dev/skills/konveyor-ecosystem/playpen-pf-mig-skills/code-migration"><img src="https://agentmods.dev/badge/skills/konveyor-ecosystem/playpen-pf-mig-skills/code-migration/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/konveyor-ecosystem/playpen-pf-mig-skills/code-migration"><img src="https://agentmods.dev/badge/skills/konveyor-ecosystem/playpen-pf-mig-skills/code-migration.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.00047 | $0.05596 |
| Opus 5 | $0.00023 | $0.02798 |
| Sonnet 5 | $0.00009 | $0.01119 |
| Haiku 4.5 | $0.00005 | $0.00560 |
Grade A, and why
code-migration 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 10d 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.
4. **Readiness polling** — poll each port with `curl`, accepting exit code 22 (HTTP 404) for port 9001 How it starts
The opening of the file, as written. The whole thing — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Migration
Migrate applications by identifying issues from multiple sources, fixing them systematically, and validating the result.
Issue Sources
Collect issues from ALL of these sources during analysis.
| Source | Examples |
|---|---|
| Kantra analysis | Deprecated APIs, breaking changes, migration patterns |
| Build errors | Compilation failures, type errors, missing deps |
| Lint errors | Style violations, unused imports |
| Test failures | Broken tests from API changes |
| Target docs | Breaking changes Kantra doesn't detect (check targets/<target>.md) |
Kantra is a static source code analysis tool that uses rules to identify migration issues in the source code.
Phase 1: Discovery
-
Explore project: Delegate to
project-explorersubagent with the path to the project. Get build command, dev server command, test commands, lint command. -
Detect OpenShift Console plugin: Check whether the project is an OpenShift Console dynamic plugin. Look for all of these indicators:
@openshift-console/dynamic-plugin-sdkinpackage.jsondependencies or devDependencies- A
console-extensions.jsonfile in the project root - A
ConsolePluginresource in any YAML/JSON file under the project
If any indicator is present, mark the project as a console plugin. Record this in
$WORK_DIR/status.mdunder a## Project Typeheading once the workspace is created. -
Build Kantra command: Ask user:
- Use custom rules? (If yes, get path)
- Enable default rulesets?
Delegate to
kantra-command-buildersubagent with the path to the project, the migration goal (target technology), custom rules path (if provided), and whether to enable default rulesets.It returns flags; you add
--input,--output, and--overwrite. -
Create workspace: Create temp directory outside the project:
WORK_DIR=$(mktemp -d -t migration-$(date +%m_%d_%y_%H))All subagent delegations below use this directory as the work directory. All migration artifacts — Kantra output, status files, screenshots, manifests, and reports — must go inside
$WORK_DIR. Never use the project directory as the work directory.
What ships with it
8 files 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.
- README.md 5.5 KB
- scripts/compare_screenshots.py 7.7 KB runs code
- scripts/filter_kantra_false_positives.py 5.1 KB runs code
- scripts/fix_deprecated_modal_wrapper.py 4.2 KB runs code
- scripts/generate_migration_report.py 19 KB runs code
- scripts/kantra_output_helper.py 10 KB runs code
- scripts/persistent_issues_analyzer.py 7.9 KB runs code
- targets/patternfly.md 9.2 KB
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.
- 10d ago First seen · 469 lines · 0 tokens per session scan A 3864d776fa42
code-migration is a skill published in the GitHub repository konveyor-ecosystem/playpen-pf-mig-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 5,596 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…