# Swapper Toolkit registers one skill, advertises three, and ships no code

> A MIT licensed skill pack that lets an AI coding assistant generate a crypto deposit link for a human to confirm, plus a separate npm SDK for embedding the same flow. Two of the three advertised skills are marked coming soon, and the published package carries neither the readme nor the licence file.

**swapperfinance/swapper-toolkit** — DeFi toolkit for AI agents and coding assistants — deposit funds, execute trades, and manage crypto wallets. Works with Claude Code, Cursor,   Windsurf, OpenClaw, CrewAI, AutoGPT, and other AI agent frameworks.

- Repository: https://github.com/swapperfinance/swapper-toolkit
- Website: https://swapper.finance
- Stars: 853 · Forks: 39
- Language: Unknown
- License: MIT
- Published: 2026-09-10 · Updated: 2026-09-10 · Language: en
- Canonical page: https://hysenlabs.com/projects/swapperfinance-swapper-toolkit

## Two of the three advertised skills are marked as coming soon

The repository describes itself as a toolkit that lets agents deposit funds, execute trades and manage wallets, and that description is repeated verbatim in the package manifest, keywords included, with entries such as trading, token-swap, dex and wallet. The document tells a narrower story. One skill, deposit, is presented as working, with triggers, an example transcript and a list of supported chains. The other two carry the same marker: `/swapper-trade` for token swaps and `/swapper-wallet` for wallet creation, funding and balance checks, each described as coming soon while still listing what it will eventually do, including slippage protection, optimal route finding and smart wallet creation with account abstraction. So the summary a search index or a package registry shows describes capabilities that the document defers, and the gap between the two texts is where a reader has to decide what they are actually getting.

## The manifest registers one skill and publishes two paths

The manifest is short enough to read in full, and two fields settle what the package is. The `claude-code` block declares its type as a skill-pack and lists exactly one entry under skills, `skills/swapper-deposit`, so the trade and wallet skills are not part of the registered pack even though the document names them. The `files` array lists two paths, `skills/` and `CLAUDE.md`, which means the published tarball contains the skill directory and that one file, and not the README and not the LICENSE, even though the document closes with an MIT line pointing at a licence file in the repository. Version is 0.1.0, the author field is the word swapper, and there is no dependencies block, no scripts block and no test command. The top level of the tree matches that minimalism: seven entries, a .claude directory, CLAUDE.md, the licence, the readme, the manifest and the skills directory.

## The open repository is instructions, the executable is an npm package

There are two install paths and they install different things. The first is one command:

```bash
npx skills add swapperfinance/swapper-toolkit
```

which adds the skill pack from the repository, for use by hosts that understand the open skills standard. The second is for people building an application, and it pulls a separate package:

```bash
npm i @swapper-finance/deposit-sdk
```

The call that follows is the whole integration surface:

```javascript
import { openSwapperModal } from "@swapper-finance/deposit-sdk";

openSwapperModal({
  integratorId: "your-integrator-id",
  dstChainId: "8453",
  dstTokenAddr: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  depositWalletAddress: "0xYourWalletAddress",
  styles: { themeMode: "dark" },
  supportedDepositOptions: ["transferCrypto", "depositWithCash"],
});
```

Nothing in the repository implements any of that. The MIT licence covers the skill files; the code that opens the modal, resolves the route and talks to the payment providers is distributed as a closed npm package under its own name.

## The safety model is a link the user opens and confirms in a browser

The safety section makes four claims: every transaction requires explicit user approval, fees and risks including slippage and gas are surfaced before confirmation, private keys are never stored or accessed, and transactions are never auto-approved. The example transcript shows what that looks like in practice. A request to deposit 100 USDC into Aave on Base is parsed into a chain, a token, a protocol and an amount, and the output is an opening deposit link followed by a line telling the user to confirm in the browser. Funds go straight into the protocol rather than into an account held by the toolkit, which is what makes the no-key-custody claim consistent with the flow. The trigger list is where the design gets interesting, because one of the four triggers is the agent detecting that a wallet has insufficient funds partway through a task. The moment an agent runs short on money is a moment it can ask for money, and that is a deliberate entry point rather than an accident.

## Ten chains in the skill, more than sixty in the infrastructure claim

The deposit skill names its supported chains explicitly: Ethereum, Base, Arbitrum, Optimism, Polygon, Fast, Solana, HyperEVM, BNB Chain and Avalanche, ten in total, with cross-chain transfers handled by Chainlink CCIP. The powered-by section makes a much larger claim about the same infrastructure, describing CCIP as cross-chain interoperability across more than sixty blockchains. The two numbers are not contradictory, since the skill is the product surface and CCIP is the transport, but they are the numbers a reader will compare when deciding whether a chain is usable. Cross-chain swapping, by contrast, is part of the trade skill, which is the one marked as coming soon, so today the bridge is a deposit route rather than a general purpose transfer between chains. In the SDK sample the destination chain is a string, 8453, the same value the deposit example names as Base, which means chain selection is the integrator's responsibility rather than something the SDK discovers.

## The deposit options are two, and one of them is cash

The sample passes `supportedDepositOptions` as a list of two values, transferCrypto and depositWithCash, which is the entire menu an integrator configures. The cash path is the one with the widest reach: the on-ramp is described as Mastercard, Visa, Apple Pay and Google Pay across more than 170 countries, with Mastercard named as the card processing partner. The orchestration behind it is not in the open repository either. Chainlink CRE is credited with end-to-end workflow orchestration for deposits, compliance and settlement, which places the compliance step inside a vendor workflow that an integrator cannot read, and the SDK is what calls into it. The practical consequence for someone embedding this is that the choice between a card payment and a crypto transfer is a two-value enum, while the compliance and settlement behaviour behind the card option belongs to infrastructure outside the repository and outside the MIT licence.

## No tagged release, and the last commit is dated 2026-04-07

State of the repository, plainly: the package is at 0.1.0, the project has published no GitHub releases at all, and the last push is dated 2026-04-07. For a pack whose value is a set of instructions that a model reads, that is the number to weigh, because a host that changes its skill format or an SDK that changes its modal parameters would show up as a change in this repository and there is no release history to tell you which version you have. The compatibility list is broad and unnamed in the version dimension: Claude Code, Cursor, Windsurf, OpenClaw, GitHub Copilot, CrewAI and AutoGPT are named, and then any framework that supports the open skills standard, with langchain appearing in the package keywords without being named in the document. The documentation link points to a separate site, and the harness for questions is that site rather than the repository, so the two places a user would look for help have different lifetimes.

## Conclusion

Swapper Toolkit is a small, readable integration rather than a system, and the smallness is its virtue: the open repository holds skill instructions, the payment logic lives in a separate npm package, and the human is the last step in the flow by design. Judge it on that basis. If you want an agent to open a funding prompt when it runs short, the deposit skill is the part that exists, and the confirmation link is the safety property that makes it reasonable to try. If you want an agent to trade or hold wallets autonomously, neither skill is shipped and the manifest does not register them, so plan on the SDK instead. Check the integrator identifier and the fee disclosure with whoever integrates the modal, and remember the last push here is dated 2026-04-07 with no tagged release at all.

## FAQ

### How do I install the Swapper AI Agent Toolkit?

With one command, npx skills add swapperfinance/swapper-toolkit, which adds the skill pack from the repository. Applications that embed the flow instead install a separate package, npm i @swapper-finance/deposit-sdk.

### Which Swapper skills exist today?

The deposit skill, for funding wallets and DeFi protocols, is the one registered in the manifest under skills/swapper-deposit. Token swap and wallet management are both described in the README as coming soon.

### Can a Swapper agent move money without asking me?

The document states that every transaction requires explicit user approval, that transactions are never auto-approved, and that private keys are never stored or accessed. The deposit example ends with a generated link and an instruction to confirm in the browser.

### Which blockchains does the Swapper deposit skill support?

Ethereum, Base, Arbitrum, Optimism, Polygon, Fast, Solana, HyperEVM, BNB Chain and Avalanche, with cross-chain transfers through Chainlink CCIP, which is described elsewhere as covering more than sixty blockchains.

### What is inside the published swapper-toolkit package?

Two paths: the skills directory and CLAUDE.md. The manifest lists no dependencies, no scripts and no test command, and the published files do not include README.md or LICENSE, though the document closes with an MIT line linking to the licence file in the repository.

## Sources

- [Issues](https://github.com/swapperfinance/swapper-toolkit/issues)
- [License: MIT](https://github.com/swapperfinance/swapper-toolkit/blob/main/LICENSE)
- [Project website](https://swapper.finance)
- [README](https://github.com/swapperfinance/swapper-toolkit/blob/main/README.md)
- [swapperfinance/swapper-toolkit on GitHub](https://github.com/swapperfinance/swapper-toolkit)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/swapperfinance-swapper-toolkit