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 eugenepyvovarov/mcpbundler-agent-skills-marketplace --skill solana-kit-migrationgit clone --depth 1 https://github.com/eugenepyvovarov/mcpbundler-agent-skills-marketplaceWrote 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/eugenepyvovarov/mcpbundler-agent-skills-marketplace/solana-kit-migration)<a href="https://agentmods.dev/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/solana-kit-migration"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/solana-kit-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/eugenepyvovarov/mcpbundler-agent-skills-marketplace/solana-kit-migration"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/solana-kit-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.02483 |
| Opus 5 | $0.00023 | $0.01241 |
| Sonnet 5 | $0.00009 | $0.00497 |
| Haiku 4.5 | $0.00005 | $0.00248 |
Grade A, and why
solana-kit-migration 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 9d 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.
This is a copy
100% identical to solana-kit-migration — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solana Kit Migration Assistant
This skill helps you navigate the transition between @solana/web3.js (v1.x) and @solana/kit (formerly web3.js 2.0), providing guidance on when to use each library and how to migrate between them.
Overview
The Solana JavaScript ecosystem has two major SDK options:
| Library | Status | Use Case |
|---|---|---|
@solana/web3.js (1.x) |
Maintenance mode | Legacy projects, Anchor-dependent apps |
@solana/kit |
Active development | New projects, performance-critical apps |
Key Decision: @solana/kit is the future, but migration isn't always straightforward.
When to Use Each Library
Use @solana/kit When:
- Starting a new project without Anchor dependencies
- Bundle size matters - Kit is tree-shakeable (26% smaller bundles)
- Performance is critical - ~200ms faster confirmation latency, 10x faster crypto ops
- Using standard programs (System, Token, Associated Token)
- Building browser applications where bundle size impacts load time
- Type safety is important - Better TypeScript support catches errors at compile time
- Using modern JavaScript - Native BigInt, WebCrypto, AsyncIterators
Use @solana/web3.js (v1.x) When:
- Using Anchor - Anchor doesn't support Kit out of the box yet
- Existing large codebase - Migration cost outweighs benefits
- Dependencies require v1 - Check if your SDKs support Kit
- Rapid prototyping - v1's OOP style may be more familiar
- Documentation/examples - More community resources for v1
Use Both (Hybrid Approach) When:
- Gradual migration - Use
@solana/compatfor interoperability - Mixed dependencies - Some libs require v1, some support Kit
- Feature-by-feature migration - Convert hot paths first
Quick Decision Flowchart
START
│
├─ New project? ─────────────────────────────────────────┐
│ │ │
│ ├─ Using Anchor? ──► YES ──► Use @solana/web3.js │
│ │ │
│ └─ No Anchor? ──► Use @solana/kit │
│ │
└─ Existing project? ────────────────────────────────────┤
│ │
├─ Performance issues? ──► Consider migration │
│ │
├─ Bundle size issues? ──► Consider migration │
│ │
└─ Working fine? ──► Stay with current SDK │
What ships with it
10 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.
- docs/edge-cases.md 14 KB
- examples/mixed-codebase/anchor-with-kit.md 11 KB
- examples/v1-to-kit/basic-transfer.md 6.9 KB
- examples/v1-to-kit/subscription-handling.md 10 KB
- examples/v1-to-kit/token-operations.md 9.6 KB
- resources/api-mappings.md 11 KB
- resources/compatibility-matrix.md 4.6 KB
- resources/package-comparison.md 6.3 KB
- scripts/analyze-migration.sh 7.1 KB runs code
- scripts/detect-patterns.js 10 KB runs code
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.
- 9d ago First seen · 347 lines · 47 tokens per session scan A 8c53b6d97912
solana-kit-migration is a skill published in the GitHub repository eugenepyvovarov/mcpbundler-agent-skills-marketplace (12 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 2,483 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to solana-kit-migration, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
solana-kit
Complete guide for @solana/kit - the modern, tree-shakeable, zero-dependency JavaScript SDK from Anza. Covers RPC connections, signers, transaction building with pipe, signing, sending, and account fetching with full TypeScript support.
solana-kit-migration
Helps developers understand when to use @solana/kit vs @solana/web3.js (v1), provides migration guidance, API mappings, and handles edge cases for Solana JavaScript SDK transitions.
viem
TypeScript patterns for low-level EVM blockchain interactions using Viem. Use when writing Node scripts, CLI tools, or backend services that read/write to Ethereum or EVM chains. Triggers on contract interactions, wallet operations, transaction signing, event watching, ABI encoding, or any non-React blockchain…
developing-genkit-js
Develop AI-powered applications using Genkit in Node.js/TypeScript. Use when the user asks about Genkit, AI agents, flows, or tools in JavaScript/TypeScript, or when encountering Genkit errors, validation issues, type errors, or API problems.
adk
Use this skill when you've got questions about the Botpress Agent Development Kit (ADK) - like when you're building a feature that involves tables, actions, tools, workflows, conversations, files, knowledge bases, triggers, or Zai.
starknet-js
Use when writing or debugging JavaScript/TypeScript that interacts with Starknet through the starknet.js SDK — building Call objects or calldata, encoding/decoding Cairo types (felt252, u256, structs, arrays, spans, ByteArray, Option/Result/custom enums), or working with contracts, accounts, providers, transactions…