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 agentmods add skills/adambien/airails/migration-advisornpx skills add AdamBien/airails --skill migration-advisorgit clone --depth 1 https://github.com/AdamBien/airailsWrote 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/adambien/airails/migration-advisor)<a href="https://agentmods.dev/skills/adambien/airails/migration-advisor"><img src="https://agentmods.dev/badge/skills/adambien/airails/migration-advisor.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.00144 | $0.01230 |
| Opus 5 | $0.00072 | $0.00615 |
| Sonnet 5 | $0.00029 | $0.00246 |
| Haiku 4.5 | $0.00014 | $0.00123 |
Grade A, and why
migration-advisor 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 6d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Advisor
The triage front door. Legacy migration is judgment-heavy and the entry-path choice is a human decision — this skill gathers the cheap signals that inform that choice, recommends a path and a sequence, and hands off. It routes, never executes: every step it recommends is invoked explicitly by a human, and each produces a reviewable artifact.
Stay shallow. The value is finishing in under a minute on a repo you have never seen. Deep vocabulary mining is /concept-extractor; behavior capture is /characterization-tests. Those are steps in the plan, not prerequisites to producing it.
Data Sources
Use whatever is present; state in the plan which were available — a plan built without git or a runnable instance is more heuristic, and must say so.
Repo probe (always)
Read-only counts and pattern hits, never comprehension:
- Platform / age — build files:
javax.*vsjakarta.*, servlet/EJB/JSF/Spring versions, target JDK; orpackage.jsonwith jQuery/AngularJS/Backbone. - Size / shape — module, package, and file counts; LOC order of magnitude; density of
*Manager/*Impl/*Util/*Facadenames (overengineering signal → concept pipeline pays off; small and clean → rearchitect directly). - External dependencies — count and identity of libraries with Java SE or platform equivalents (the replatform/simplifier signal).
- Test coverage — presence and size of a test source tree (near-zero → characterization must come first; "1:1 lift" is risky).
- Surfaces — JAX-RS resources,
web.xmlmappings, queue config, batch jobs; whether a runnable artifact exists (is characterization feasible, on which surface).
Git history (if .git present)
Aggregate git log / shortlog / --numstat, not per-file blame:
- Liveness — last commit date, commit frequency: frozen (experts likely gone → lean on recorded behavior and async questionnaires) vs. active (strangle alongside ongoing work).
- Bus factor —
git shortlog -sne: contributor count and whether the top authors are recent. Pre-fills the interview's expert-availability question with names. - Hotspots — churn per file/package: where behavior is volatile and characterization should concentrate.
- Temporal coupling — files that change together: empirical evidence that latent structure exists and the carve path will pay off. Note it; do not carve — that is
/bc-carver. - Code age — old untouched code is safe to lift; recently churned code is where lift risk concentrates.
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.
- 6d ago First seen · 67 lines · 144 tokens per session scan A b8bdb4ded7d8
migration-advisor is a skill published in the GitHub repository AdamBien/airails (48 stars, last pushed yesterday), licensed MIT. It adds 144 tokens to every session and 1,230 once invoked, about $0.0007 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.
Other skills, from other repositories
authoring-java-sdk-tasks
Writes Airflow task logic in Java, Kotlin, or any JVM language using the Airflow Java SDK. Use when the user wants to implement Airflow tasks in Java/JVM, asks about @Builder.Dag/@Builder.Task/@Builder.XCom, the Task/BundleBuilder interfaces, reading connections/variables/XComs from Java, the JSON-to-Java type…
configuring-airflow-language-sdks
Configures Airflow to run language SDK tasks (Java, Go, and future native SDKs) — register a coordinator, map a queue to it, ensure the runtime/artifact on workers, and tune coordinator options. Use when the user wants Airflow to route a queue to a native-language coordinator, asks about the [sdk]…
help
OrchestKit help directory with categorized skill listings. Use when discovering skills for a task, finding the right workflow, or browsing capabilities.
jackson-3-migration
Migrer Jackson 2.x til Jackson 3.x (tools.jackson) i Kotlin/Java-prosjekter — automatisert OpenRewrite-pass pluss manuell Kotlin-spesifikk opprydding og verifisering.
java-to-kotlin
Trinnvis Java-til-Kotlin-migrering med rammeverk-bevisste transformasjoner for Spring, Ktor og Nav-mønstre.
js-gof
Apply Gang of Four and related design patterns in JavaScript and TypeScript. Use when implementing creational, structural, or behavioral patterns, or when the user mentions factories, builder, prototype, flyweight, singleton, object pool, adapter, wrapper, decorator, proxy, bridge, composite, facade, chain of…