Alchemy Upgrade Migration
jeremylongshore/tons-of-skills-marketplace
Migrate archived Alchemy JavaScript SDK integrations to current capability-specific clients with parity, canary, and rollback evidence.
Walks an agent through Jupiter's express verification flow for a Solana token mint: eligibility check, payment transaction, execution and optional metadata update.
Install Jupiter Token Verification Flow
$ npx skills add internet-court/internet-court-skill --skill jupiter-vrfd -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-vrfd --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-vrfd .claude/skills/jupiter-vrfd && 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-vrfd" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-vrfd into .claude/skills/jupiter-vrfd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-vrfd", 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-vrfdType 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-vrfd -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-vrfd --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-vrfd .agents/skills/jupiter-vrfd && 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-vrfd" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-vrfd into .agents/skills/jupiter-vrfd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-vrfd", 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-vrfd -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-vrfd --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-vrfd .cursor/skills/jupiter-vrfd && 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-vrfd" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-vrfd into .cursor/skills/jupiter-vrfd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-vrfd", 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-vrfd--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-vrfd -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install internet-court/internet-court-skill jupiter-vrfd --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-vrfd .gemini/skills/jupiter-vrfd && 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-vrfd" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-vrfd into .gemini/skills/jupiter-vrfd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-vrfd", 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-vrfdInstalls 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-vrfd -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-vrfd .github/skills/jupiter-vrfd && 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-vrfd" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-vrfd into .github/skills/jupiter-vrfd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-vrfd", 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-vrfd -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-vrfd --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-vrfd .opencode/skills/jupiter-vrfd && 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-vrfd" agent skill from https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-vrfd into .opencode/skills/jupiter-vrfd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jupiter-vrfd", 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-vrfd- GitHub stars
- 6.6k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 397 words
- Files
- 5 (incl. references)
- Skills in repo
- 80
- Repo updated
- First seen
- Licence
- MIT
At a glance
Walks an agent through Jupiter's express verification flow for a Solana token mint: eligibility check, payment transaction, execution and optional metadata update.
- Checking whether a Solana token is eligible for Jupiter verification
- SKILL.md covers Use/Do Not Use, Intent Router, Eligibility Decision Matrix and Examples, plus 3 more sections
- Reaches api.jup.ag
- Preparing and executing the paid verification submission for a token
What it does
This skill routes an agent through Jupiter's public token verification flow for a Solana token mint. The flow costs 1000 JUP and needs an `x-api-key` from the Jupiter developer portal. Three endpoints on `api.jup.ag` map to the steps: a GET to check eligibility, a GET to craft the payment transaction for a sender address, and a POST to sign and execute the payment.
A decision matrix on the `canVerify` and `canMetadata` flags picks the action: verification with metadata, verification only, metadata only, or a full stop that shows the returned error messages when neither is allowed. The skill rules out private or internal routes, fetching existing metadata from non-public endpoints, and swaps, trading or other Jupiter flows. Example files and an API reference ship with it.
When your agent uses it
- Checking whether a Solana token is eligible for Jupiter verification
- Preparing and executing the paid verification submission for a token
- Submitting a metadata-only paid update when verification is not allowed
Example prompts
- “Check whether my token mint is eligible for Jupiter express verification.”
- “Craft the payment transaction for verifying my token from this sender address and show it to me before anything is signed.”
- “Our token can update metadata but not verification. Walk me through the metadata-only submission.”
Requirements
- A Jupiter API key from developers.jup.ag
- 1000 JUP to pay for a verification
- A wallet able to sign the payment transaction
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.agverified.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 Token Verification Flow loads about 1.1k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 397 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). 397 words, ~1,071 tokens.
Download SKILL.mdSave it as
.claude/skills/jupiter-vrfd/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- jupiter-vrfd
- description
- Use when a user mentions Jupiter token verification, VRFD eligibility, paying 1000 JUP to verify a token, submitting a verification request, or updating metadata via the Jupiter express verification flow.
- license
- MIT
- metadata.author
- jup-ag
- metadata.version
- 1.0.1
- tags
- jupiter, jup-ag, jupiter-vrfd, token-verification, verified, solana
Jupiter Token Verification
This skill routes agents through the public Jupiter token-verification flow for a Solana token mint.
Base URL: https://api.jup.ag
Auth: x-api-key from developers.jup.ag (required)
Cost: 1000 JUP
Use/Do Not Use
Use when:
- checking whether a token is eligible for submission
- crafting and signing the submission payment transaction
- executing the submission flow
- optionally updating token metadata as part of the submission
- submitting a metadata-only paid update when eligibility allows metadata but not verification
Do not use when:
- the agent would need private or internal routes
- the agent needs to fetch or merge existing metadata from non-public endpoints
- the user wants swaps, trading, or unrelated Jupiter flows
Triggers: verify token, submit verification, check eligibility, craft payment transaction, execute payment, pay for verification, update token metadata, metadata-only submission
Intent Router
| User intent | Endpoint | Method |
|---|---|---|
| Check eligibility | /tokens/v2/verify/express/check-eligibility?tokenId={TOKEN_ID} | GET |
| Craft payment transaction | /tokens/v2/verify/express/craft-txn?senderAddress={SENDER_ADDRESS} | GET |
| Sign and execute payment | /tokens/v2/verify/express/execute | POST |
Eligibility Decision Matrix
canVerify | canMetadata | Action |
|---|---|---|
true | true | verification+metadata (if user has metadata) or verification only |
true | false | verification only, omit tokenMetadata |
false | true | metadata-only |
false | false | STOP — show verificationError / metadataError to user |
Examples
Load these on demand:
- API Reference for the exact request and response shapes, accepted input formats, normalization rules, submission-mode field requirements, and token metadata fields. This is the source of truth for request construction.
- Verify when the user wants to execute a request and has confirmed the paying wallet details
Show full SKILL.md (165 more words)Show less
Agent Operating Rules
- Reuse as much as possible from the user's first message. Ask only for missing required fields.
- Never ask the user to paste a raw private key or seed phrase into chat.
- Never print secret values. Only mention non-sensitive file paths, key names, and derived public addresses.
- Do not claim a request was submitted unless you have a real API response or the user explicitly ran the local script themselves.
- If the current agent runtime cannot reach the network, install dependencies, or access local signer files, stop before execution and hand the user the exact local steps instead of fabricating progress.
Execution Notes
For execute requests in constrained agent environments:
- outbound HTTP and package installation may require approval or user permission
- equivalent shell and package-manager commands are fine; do not block on a specific CLI if the environment already has an equivalent way to run the same steps
Resources
- Jupiter Burn Multisig:
8gMBNeKwXaoNi9bhbVUWFt4Uc5aobL9PeYMXfYDMePE2 - JUP Token Mint:
JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN - Jupiter Docs: developers.jup.ag
- Jupiter Verified: verified.jup.ag
© 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 4 other files (references) in vendored/jupiter/jupiter-vrfd of internet-court/internet-court-skill.
- SKILL.md
- LICENSE
- README.md
- examples/verify.md
- references/api-reference.md
Open the folder on GitHubat commit fa89195
Compare with similar skills
Jupiter Token Verification Flow 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 Token Verification Flow this skillinternet-court/internet-court-skill | 6.6k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Alchemy Upgrade Migrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Helius Phantomsendaifun/skills | 130 | 1 repos | ~4.7k | Automated safety check: Notes | MIT | |
| CCXT Crypto Exchange Library2025Emma/vibe-coding-cn | 23k | 1 repos | ~4.4k | Automated safety check: Pass | MIT | |
| Whale Trackingalsk1992/CloddsBot | 3k | — | ~2k | Automated safety check: Pass | MIT | |
| CoinGecko API Reference2025Emma/vibe-coding-cn | 23k | 1 repos | ~646 | Automated safety check: Pass | MIT |
Similar skills
Helius Phantom
sendaifun/skills
Build frontend Solana applications with Phantom Connect SDK and Helius infrastructure.
CCXT Crypto Exchange Library
2025Emma/vibe-coding-cn
Reference help for the CCXT library covering crypto exchange APIs, market data, trading and order management across 150+ exchanges in JavaScript, Python and PHP.
Whale Tracking
alsk1992/CloddsBot
Monitor whale trades on Polymarket and crypto chains (Solana, ETH, Polygon, ARB, Base, OP)
CoinGecko API Reference
2025Emma/vibe-coding-cn
CoinGecko API documentation - cryptocurrency market data API, price feeds, market cap, volume, historical data. Use when integrating CoinGecko API, building…
Swapper Deposit
swapperfinance/swapper-toolkit
Deposit and bridge funds into a wallet or protocol using Swapper Finance.
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
Works with
Categories
Questions about Jupiter Token Verification Flow
What does Jupiter Token Verification Flow do?
Walks an agent through Jupiter's express verification flow for a Solana token mint: eligibility check, payment transaction, execution and optional metadata update. This skill routes an agent through Jupiter's public token verification flow for a Solana token mint. The flow costs 1000 JUP and needs an `x-api-key` from the Jupiter developer portal.
When should I use Jupiter Token Verification Flow?
Jupiter Token Verification Flow fits situations like: checking whether a Solana token is eligible for Jupiter verification; preparing and executing the paid verification submission for a token; submitting a metadata-only paid update when verification is not allowed.
How do I install Jupiter Token Verification Flow in Claude Code?
Run `npx skills add internet-court/internet-court-skill --skill jupiter-vrfd -a claude-code`. Or copy the skill folder (vendored/jupiter/jupiter-vrfd in internet-court/internet-court-skill) into .claude/skills/jupiter-vrfd in your project. Claude Code loads it when a task matches its description.
How do I install Jupiter Token Verification Flow in Codex?
Run `npx skills add internet-court/internet-court-skill --skill jupiter-vrfd -a codex`. Or copy the skill folder (vendored/jupiter/jupiter-vrfd in internet-court/internet-court-skill) into .agents/skills/jupiter-vrfd in your project. Codex loads it when a task matches its description.
Can I use Jupiter Token Verification Flow 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-vrfd -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-vrfd, .gemini/skills/jupiter-vrfd, .github/skills/jupiter-vrfd and .opencode/skills/jupiter-vrfd in your project.
What does Jupiter Token Verification Flow need to run?
SKILL.md names no scripts, command-line tools or credentials: Jupiter Token Verification Flow is instructions for the agent only. Our summary lists: A Jupiter API key from developers.jup.ag; 1000 JUP to pay for a verification; A wallet able to sign the payment transaction.
Does Jupiter Token Verification Flow access the network?
SKILL.md names 3 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 and verified.jup.ag. This is read from the text; nothing was executed.
Is Jupiter Token Verification Flow 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 Token Verification Flow use?
Jupiter Token Verification Flow 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 Token Verification Flow use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.2k tokens, read only when the agent opens those files.
What are the alternatives to Jupiter Token Verification Flow?
Skills that share tags, products or a category with Jupiter Token Verification Flow: Alchemy Upgrade Migration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Helius Phantom (sendaifun/skills, 130 stars), CCXT Crypto Exchange Library (2025Emma/vibe-coding-cn, 23k stars) and Whale Tracking (alsk1992/CloddsBot, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jupiter Token Verification Flow?
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.