agentleFS
InjectiveLabsInjectiveLabs/agent-skills/skills/injective-trading-bridge/SKILL.md

injective-trading-bridge

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

Bridge tokens to and from Injective using deBridge DLN (fast, cross-chain) or Peggy (Ethereum canonical bridge). Supports inbound bridges from Arbitrum, Ethereum, Base, Polygon, BSC, Avalanche, and Optimism into Injective, and outbound bridges from Injective to any deBridge-supported chain. Get quotes before executing. Requires the Injective MCP server to be connected.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always get a quote first (bridge_debridge_quote / bridge_debridge_inbound_quote), *before* executing.

    line 18
  2. Very specific:

    If the source chain has no configured default RPC, provide rpcUrl explicitly.

    line 40
  3. Very specific:

    After an inbound bridge, tokens arrive on Injective EVM.

    line 41
  4. Distinctive:

    If these skills are not available, selectively run the following commands to install them:

    line 123
  5. Distinctive:

    When integrating deBridge DLN in a browser frontend:

    line 131
  6. Distinctive:

    Balance doesn't auto-refresh: after bridging. Add an explicit refresh button next to the balance display, or poll the balance on a timer …

    line 134

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Injective Trading Bridge, Skill Guide

Move tokens cross-chain to/from Injective using two bridge protocols:

  • deBridge DLN - fast (minutes), supports Arbitrum, Base, Ethereum, Polygon, BSC, Avalanche, Optimism
  • Peggy - Injective's canonical Ethereum bridge (~30 min, decentralized)

Always get a quote first (bridge_debridge_quote / bridge_debridge_inbound_quote), before executing.

When to apply

  • Bridging tokens from other networks into Injective
  • Bridging tokens from Injective into other networks

Sample prompts: ./references/sample-prompts.md

Important

Common tokens and network info

See ./references/common-tokens.md for common tokens.

See ./references/common-networks.md for common networks.

Notes

  • deBridge DLN settles in minutes. Quote includes fee breakdown and estimated receive amount.
  • The inbound flow reuses the Injective wallet's private key on the source EVM chain
    • this works because Injective uses the same secp256k1 curve as Ethereum.
  • If the source chain has no configured default RPC, provide rpcUrl explicitly.
  • After an inbound bridge, tokens arrive on Injective EVM. Use subaccount_deposit to move them into the trading subaccount.

Activities

Bridge tokens from Injective to other network using DeBridge

Step 1 - Obtain quote:

bridge_debridge_quote
  address: inj1...         ← sender (Injective)
  srcTokenDenom: usdt      ← denom on Injective (symbol or full denom)
  amount: 50               ← human-readable amount
  dstChain: arbitrum       ← or: base, ethereum, polygon, bsc, avalanche, optimism
  dstTokenAddress: 0xaf88d065e77c8cc2239327c5edb3a432268e5831   ← USDC on Arbitrum
  recipient: 0x...         ← EVM address on destination chain

Step 2 - Execute quote:

bridge_debridge_send
  address: inj1...
  password: ****
  srcTokenDenom: usdt
  amount: 50
  dstChain: arbitrum
  dstTokenAddress: 0xaf88...
  recipient: 0x...

Bridge tokens from other network to Injective using DeBridge

The Injective wallet's private key (secp256k1) signs on both chains, the same private key works on EVM chains.

Step 1 - Obtain quote:

bridge_debridge_inbound_quote
  srcChain: arbitrum       ← or chain ID: 42161
  srcTokenAddress: 0xaf88d065e77c8cc2239327c5edb3a432268e5831   ← USDC on Arbitrum
  amount: 50
  dstTokenAddress: 0x88f7f2b685f9692caf8c478f5badf09ee9b1cc13   ← USDT on Injective EVM
  recipient: inj1...       ← or 0x EVM address on Injective

Step 2 - Execute quote:

This performs an ERC20 approve + bridge transaction on source chain.

bridge_debridge_inbound_send
  address: inj1...         ← Injective wallet (key used on source chain too)
  password: ****
  srcChain: arbitrum
  srcTokenAddress: 0xaf88...
  amount: 50
  dstTokenAddress: 0x88f7...
  recipient: inj1...

Note: You need to pay transaction fees on both networks.

Bridge tokens from Injective to Ethereum using Peggy

This method is slower, but also decentralized. Expect to take ~30min.

bridge_withdraw_to_eth
  address: inj1...
  password: ****
  denom: peggy0xdac17f958d2ee523a2206206994597c13d831ec7   ← USDT denom on Injective
  amount: 100
  ethRecipient: 0x...

Related skills

  • injective-mcp-servers

If these skills are not available, selectively run the following commands to install them:

npx skills add InjectiveLabs/agent-skills --skill injective-mcp-servers

Browser-Based Bridge UX Notes

When integrating deBridge DLN in a browser frontend:

  • Arbitrum USDC → Injective USDT is the most common path. Takes ~1-3 minutes.
  • Balance doesn't auto-refresh after bridging. Add an explicit refresh button next to the balance display, or poll the balance on a timer after bridge submission.
  • Don't block on bridge confirmation — show "Transaction submitted!" and let the user continue. The USDT arrives async.
  • User needs ETH on Arbitrum for gas. Make this clear in the UI before the bridge flow.

Prerequisites

  • Injective MCP server must be running
  • User prompts should be issued from an AI tool that is configured to talk to the Injective MCP server

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.