Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2.
Install Jupiter Swap Migration
$ npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-swap-migration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/vendored/jupiter/jupiter-swap-migration .claude/skills/jupiter-swap-migration && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jupiter-swap-migration" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration into .claude/skills/jupiter-swap-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-swap-migration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-swap-migration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/vendored/jupiter/jupiter-swap-migration .agents/skills/jupiter-swap-migration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jupiter-swap-migration" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration into .agents/skills/jupiter-swap-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-swap-migration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-swap-migration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/vendored/jupiter/jupiter-swap-migration .cursor/skills/jupiter-swap-migration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jupiter-swap-migration" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration into .cursor/skills/jupiter-swap-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-swap-migration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/internet-court/internet-court-skill.git --path vendored/jupiter/jupiter-swap-migration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-swap-migration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/vendored/jupiter/jupiter-swap-migration .gemini/skills/jupiter-swap-migration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jupiter-swap-migration" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration into .gemini/skills/jupiter-swap-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-swap-migration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install internet-court/internet-court-skill jupiter-swap-migrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/vendored/jupiter/jupiter-swap-migration .github/skills/jupiter-swap-migration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jupiter-swap-migration" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration into .github/skills/jupiter-swap-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-swap-migration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-swap-migration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/vendored/jupiter/jupiter-swap-migration .opencode/skills/jupiter-swap-migration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jupiter-swap-migration" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration into .opencode/skills/jupiter-swap-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-swap-migration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jupiter-swap-migration- GitHub stars
- 6.6k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 473 words
- Files
- 6
- Skills in repo
- 80
- Repo updated
- First seen
- Licence
- MIT
At a glance
Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2.
- Works in 10 steps: URL audit: Search codebase for… → Parameter rename: userPublicKey → taker… → swapMode removal: V2 only supports… → …
- Migrating existing Jupiter swap integrations
- SKILL.md covers Use/Do Not Use, Migration Paths, Path Details and Post-Migration Checklist, plus 2 more sections
- Reaches api.jup.ag
What it does
Jupiter Swap Migration is an agent skill from internet-court/internet-court-skill. Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2. Use when migrating existing Jupiter swap integrations, updating base URLs, or transitioning from quote+swap-instructions to the unified build endpoint.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `README.md`, `examples/metis-to-build.md` and `examples/metis-to-order.md`).
It sits in Development, covering Code migrations. The repository describes itself as: The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, and dispute resolution as one open, catch-all… The licence is MIT.
When your agent uses it
- Migrating existing Jupiter swap integrations
- Updating base URLs
- Transitioning from quote+swap-instructions to the unified build endpoint
Example prompts
- “/jupiter-swap-migration”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- URL audit: Search codebase for ultra-api.jup.ag, /ultra/v1/, /swap/v1/quote, /swap/v1/swap-instructions — all should be replaced
- Parameter rename: userPublicKey → taker (for /build path)
- swapMode removal: V2 only supports ExactIn. If using ExactOut, redesign the flow — this mode is no longer available
- slippageBps default: /build defaults to 50 bps if omitted. For /order, verify the default if your integration relies on a specific value
- Response field names: Verify your code uses inputAmountResult/outputAmountResult for the /execute response (the canonical v2 field names)
- ALT handling: If using /build, switch from addressLookupTableAddresses (array) to addressesByLookupTableAddress (object) — remove RPC ALT…
- Fee event parsing: V2 instructions don't emit fee events — update any transaction parser that depends on them
- Route plan format: If parsing route plans, use bps field (canonical) instead of percent
- Error codes: Update error handling to match Swap v2 error codes
- Test: Run end-to-end swap on devnet/mainnet with small amount to verify
What it can do on your machine
Read from SKILL.md and the folder at commit fa89195. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
api.jup.ag
Also links to:
developers.jup.ag
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jupiter Swap Migration loads about 1.2k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 473 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from internet-court/internet-court-skill at commit fa89195, republished under its MIT licence (© internet-court). 473 words, ~1,233 tokens.
Download SKILL.mdSave it as
.claude/skills/jupiter-swap-migration/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- jupiter-swap-migration
- description
- Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2. Use when migrating existing Jupiter swap integrations, updating base URLs, or transitioning from quote+swap-instructions to the unified build endpoint.
- license
- MIT
- metadata.author
- jup-ag
- metadata.version
- 1.1.0
- tags
- jupiter, swap-migration, metis, ultra, swap-v2, jup-ag
Jupiter Swap Migration Guide
Migrate existing Jupiter swap integrations from Metis (v1) or Ultra to the unified Swap API v2.
Target Base URL: https://api.jup.ag/swap/v2
Auth: x-api-key from developers.jup.ag (unchanged)
Use/Do Not Use
Use when:
- Migrating code that calls
api.jup.ag/swap/v1/quote,api.jup.ag/swap/v1/swap-instructions, orultra-api.jup.ag. - Updating Jupiter swap endpoints to v2.
- Switching from Metis two-step flow to the unified
/buildor/orderendpoint.
Do not use when:
- Building a new Jupiter integration from scratch (use
integrating-jupiterskill instead). - Working with non-swap Jupiter APIs (Lend, Trigger, Recurring, etc.).
Triggers: ultra, metis, ultra swap, ultra api, ultra-api.jup.ag, /ultra/v1, swap/v1, swap-instructions, migrate swap, ultra migration, metis migration, swap v1 to v2, v1 to v2, upgrade jupiter, swap-instructions deprecated, deprecated swap, old jupiter api, swap upgrade, update swap api, quote endpoint deprecated, swap stopped working, swap broken, ExactOut removed, swapMode removed, userPublicKey, parameter rename, addressLookupTable, response format changed
Migration Paths
| Source | Target | Effort | When to choose |
|---|---|---|---|
Ultra → /order | GET /swap/v2/order + POST /swap/v2/execute | Minimal (URL change only) | Default for Ultra users |
Metis → /build | GET /swap/v2/build | Moderate (parameter + response mapping) | Need transaction composability |
Metis → /order | GET /swap/v2/order + POST /swap/v2/execute | Moderate (flow change) | Don't need tx modification, want managed execution |
Path Details
Each path has a dedicated example with before/after code, parameter mappings, and response changes:
- Path 1: Ultra →
/order— Minimal migration, base URL change only - Path 2: Metis →
/build— Consolidates 2 calls into 1, parameter and response mapping - Path 3: Metis →
/order— Flow change to managed execution with multi-router competition
Show full SKILL.md (232 more words)Show less
Post-Migration Checklist
- URL audit: Search codebase for
ultra-api.jup.ag,/ultra/v1/,/swap/v1/quote,/swap/v1/swap-instructions— all should be replaced - Parameter rename:
userPublicKey→taker(for/buildpath) swapModeremoval: V2 only supportsExactIn. If usingExactOut, redesign the flow — this mode is no longer availableslippageBpsdefault:/builddefaults to 50 bps if omitted. For/order, verify the default if your integration relies on a specific value- Response field names: Verify your code uses
inputAmountResult/outputAmountResultfor the/executeresponse (the canonical v2 field names) - ALT handling: If using
/build, switch fromaddressLookupTableAddresses(array) toaddressesByLookupTableAddress(object) — remove RPC ALT resolution code - Fee event parsing: V2 instructions don't emit fee events — update any transaction parser that depends on them
- Route plan format: If parsing route plans, use
bpsfield (canonical) instead ofpercent - Error codes: Update error handling to match Swap v2 error codes
- Test: Run end-to-end swap on devnet/mainnet with small amount to verify
Sunset
Remove this skill once Jupiter decommissions the v1 (/swap/v1) endpoints and the Ultra (ultra-api.jup.ag) domain. At that point all integrations will already be on v2.
Review by: 2026-09-01 — check if v1/Ultra endpoints have been decommissioned.
References
Migration is split into three profile-targeted guides (the old single migration page no longer exists):
© internet-court, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files in vendored/jupiter/jupiter-swap-migration of internet-court/internet-court-skill.
- SKILL.md
- LICENSE
- README.md
- examples/metis-to-build.md
- examples/metis-to-order.md
- examples/ultra-to-order.md
Open the folder on GitHubat commit fa89195
Compare with similar skills
Jupiter Swap Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jupiter Swap Migration this skillinternet-court/internet-court-skill | 6.6k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Next Cache Components Adoptionvercel/next.js | 143k | 6 repos | ~8.3k | Automated safety check: Pass | MIT | |
| Deprecate R Functions and Argumentstidyverse/dplyr | 5.1k | 1 repos | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
- Official
Next Cache Components Adoption
vercel/next.js
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces.
Deprecate R Functions and Arguments
tidyverse/dplyr
Walks through deprecating an R function or argument in a package: lifecycle warning, silenced tests, a new snapshot test, documentation badge and NEWS entry.
Rust Path Types
openinterpreter/openinterpreter
Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.
More from internet-court/internet-court-skill
All 80 skills in this repoKleros IPFS Upload
internet-court/internet-court-skill
Uploads one Kleros-related file per paid request to IPFS through the Kleros x402 gateway for 0.01 USDC on Base, returning a CID that Kleros contracts can reference.
0G Compute Network Guide
internet-court/internet-court-skill
Guides building on the 0G Compute Network, a decentralized GPU marketplace for AI inference and fine-tuning, with SDK patterns and CLI commands.
PNP Prediction Markets on Solana
internet-court/internet-court-skill
Creates, trades and settles permissionless prediction markets on Solana with any SPL token as collateral, including social-media and custom-oracle markets.
BNB Chain MCP Server
internet-court/internet-court-skill
Connects an agent to the BNB Chain MCP server to read blocks and contracts, move tokens and NFTs, register ERC-8004 agents and use Greenfield storage.
GenLayer ERC-7710 Connector
internet-court/internet-court-skill
Specifies how a GenLayer Intelligent Contract decision about an agent's performance becomes an ERC-7710 revocation or policy change, through a relayer or bridge and an EVM controller.
GenLayer Agent Supervision Adapter
internet-court/internet-court-skill
Specifies how a GenLayer Intelligent Contract should supervise an AI agent, with review rubrics, evidence schemas and continue, warn, constrain or revoke decisions.
Related
Categories
Questions about Jupiter Swap Migration
What does Jupiter Swap Migration do?
Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2. Jupiter Swap Migration is an agent skill from internet-court/internet-court-skill. Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2.
When should I use Jupiter Swap Migration?
Jupiter Swap Migration fits situations like: migrating existing Jupiter swap integrations; updating base URLs; transitioning from quote+swap-instructions to the unified build endpoint.
How do I install Jupiter Swap Migration in Claude Code?
Run `npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a claude-code`. Or copy the skill folder (vendored/jupiter/jupiter-swap-migration in internet-court/internet-court-skill) into .claude/skills/jupiter-swap-migration in your project. Claude Code loads it when a task matches its description.
How do I install Jupiter Swap Migration in Codex?
Run `npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a codex`. Or copy the skill folder (vendored/jupiter/jupiter-swap-migration in internet-court/internet-court-skill) into .agents/skills/jupiter-swap-migration in your project. Codex loads it when a task matches its description.
Can I use Jupiter Swap Migration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add internet-court/internet-court-skill --skill jupiter-swap-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jupiter-swap-migration, .gemini/skills/jupiter-swap-migration, .github/skills/jupiter-swap-migration and .opencode/skills/jupiter-swap-migration in your project.
What does Jupiter Swap Migration need to run?
SKILL.md names no scripts, command-line tools or credentials: Jupiter Swap Migration is instructions for the agent only.
Does Jupiter Swap Migration access the network?
SKILL.md names 2 domains. In commands or code: api.jup.ag; the agent is likely to contact it when it follows the instructions. As links in the text: developers.jup.ag. This is read from the text; nothing was executed.
Is Jupiter Swap Migration safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jupiter Swap Migration use?
Jupiter Swap Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Jupiter Swap Migration use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jupiter Swap Migration?
Skills that share tags, products or a category with Jupiter Swap Migration: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars), ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars) and Next Cache Components Adoption (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jupiter Swap Migration?
internet-court (a GitHub organization) maintains it in internet-court/internet-court-skill, which has 6,551 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on August 19, 2026.
Source: internet-court/internet-court-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.