Agent skill

Tokenized Agents

by LeoYeAI in LeoYeAI/openclaw-master-skills

Build payment flows for Pump Tokenized Agents using @pump-fun/agent-payments-sdk.

MITAuto-check: notesBackend & APIs

Install Tokenized Agents

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill tokenized-agents -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills tokenized-agents --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pump-fun-tokenized-agents .claude/skills/tokenized-agents && rm -rf skills-src

Use ~/.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/

Facts

Skill name
tokenized-agents
GitHub stars
2.2k
Token cost
~4.6k tokens
SKILL.md length
1,219 words
Files
4 (incl. references)
Skills in repo
972
Repo updated
First seen
Licence
MIT

At a glance

Build payment flows for Pump Tokenized Agents using @pump-fun/agent-payments-sdk.

  • Works in 3 steps: Generate Invoice Parameters (Server) → Build Transaction and Serialize as… → Deserialize, Sign, and Send the…
  • Accepting payments
  • SKILL.md covers Before You Start — Gather…, Safety Rules, Supported Currencies and Environment Variables, plus 8 more sections
  • Calls npm; reaches rpc.solanatracker.io and api.mainnet-beta.solana.com

What it does

Tokenized Agents is an agent skill from LeoYeAI/openclaw-master-skills. Build payment flows for Pump Tokenized Agents using @pump-fun/agent-payments-sdk. Use when accepting payments, building accept-payment transactions, integrating Solana wallets, or verifying that a user has paid an invoice on-chain.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `_meta.json`, `references/SCENARIOS.md` and `references/WALLET_INTEGRATION.md`).

It sits in Backend & APIs, covering Forms and invoices and Smart contracts. It works with Solana and Circle USDC. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Accepting payments
  • Building accept-payment transactions
  • Integrating Solana wallets
  • Verifying that a user has paid an invoice on-chain

Example prompts

  • “/tokenized-agents”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Generate Invoice Parameters (Server)
  2. Build Transaction and Serialize as Base64 (Server)
  3. Deserialize, Sign, and Send the Transaction (Client)

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. 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

    Shell commands in SKILL.md call:

    • npm

    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:

    • rpc.solanatracker.io
    • api.mainnet-beta.solana.com
    • rpc.ankr.com

    Also links to:

    • raw.githubusercontent.com

    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

Tokenized Agents loads about 4.6k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 1,219 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.7k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:43
    Create a `.env` (or `.env.local` for Next.js) file with the following:

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 LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,219 words, ~4,577 tokens.

Download SKILL.mdSave it as .claude/skills/tokenized-agents/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
tokenized-agents
description
Build payment flows for Pump Tokenized Agents using @pump-fun/agent-payments-sdk. Use when accepting payments, building accept-payment transactions, integrating Solana wallets, or verifying that a user has paid an invoice on-chain.
metadata.author
pump-fun
metadata.version
1.0

Pump Tokenized Agent Payments

Pump Tokenized Agents are AI agents whose revenue is linked to a token on pump.fun. The @pump-fun/agent-payments-sdk lets you build payment transactions and verify invoices on Solana.

Before You Start — Gather Required Information

Before writing any code, ask the user for the following if not already provided:

  1. Agent token mint address — the token mint created when the agent coin was launched on pump.fun.
  2. Payment currency — USDC or SOL (determines the currencyMint).
  3. Price / amount — how much to charge per request, in the currency's smallest unit.
  4. Service to deliver — what the agent should do after payment is confirmed (generate content, access an API, etc.).
  5. Solana RPC — which solana rpc to use, we have some defaults if they don't provide.

Do not assume these values. If any are missing, ask the user before proceeding.

Safety Rules

  • NEVER log, print, or return private keys or secret key material.
  • NEVER sign transactions on behalf of a user — you build the instruction, the user signs.
  • Always validate that amount > 0 before creating an invoice.
  • Always ensure endTime > startTime and both are valid Unix timestamps.
  • Use the correct decimal precision for the currency (6 decimals for USDC, 9 for SOL).
  • Always verify payments on the server using validateInvoicePayment before delivering any service. Never trust the client alone — clients can be spoofed.

Supported Currencies

CurrencyDecimalsSmallest unit example
USDC61000000 = 1 USDC
Wrapped SOL91000000000 = 1 SOL

Environment Variables

Create a .env (or .env.local for Next.js) file with the following:

env
# Solana RPC — server-side (used to build transactions and verify payments)
SOLANA_RPC_URL=https://rpc.solanatracker.io/public

# Solana RPC — client-side (used by wallet adapter in the browser)
NEXT_PUBLIC_SOLANA_RPC_URL=https://rpc.solanatracker.io/public

# The token mint address of your tokenized agent on pump.fun
AGENT_TOKEN_MINT_ADDRESS=<your-agent-mint-address>

# Payment currency mint
# USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
# SOL (wrapped): So11111111111111111111111111111111111111112
CURRENCY_MINT=EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v

RPC for mainnet-beta: The default Solana public RPC (https://api.mainnet-beta.solana.com) does not support sending transactions. Ask the user for an RPC provider, If the user has not provided their own RPC URL, use one of these free mainnet-beta endpoints that support sendTransaction:

  • Solana Tracker — https://rpc.solanatracker.io/public
  • Ankr — https://rpc.ankr.com/solana

Read these values from process.env at runtime. Never hard-code mint addresses or RPC URLs.

Install

bash
npm install @pump-fun/agent-payments-sdk@3.0.0 @solana/web3.js@^1.98.0
Dependency Compatibility — IMPORTANT

@pump-fun/agent-payments-sdk depends on @solana/web3.js and @solana/spl-token. When the app also installs these packages directly, mismatched versions can cause runtime errors.

Rules:

  1. Before installing @solana/web3.js, @solana/spl-token, or any @solana/wallet-adapter-* package, first check what versions @pump-fun/agent-payments-sdk declares in its own package.json (inspect it via npm info @pump-fun/agent-payments-sdk dependencies). Install the same ranges — or ranges that resolve to the same major.minor — so npm/pnpm hoists a single copy instead of two.
  2. Never blindly install "latest" for these shared packages. Always prefer the version that is most compatible with the latest @pump-fun/agent-payments-sdk.
  3. If the project already has these packages at different versions, align them to match the SDK and re-install.

SDK Setup

PumpAgent is the main class. It can build payment instructions and verify invoices.

typescript
import { PumpAgent } from "@pump-fun/agent-payments-sdk";
import { PublicKey } from "@solana/web3.js";

const agentMint = new PublicKey(process.env.AGENT_TOKEN_MINT_ADDRESS!);
Constructor
typescript
new PumpAgent(mint: PublicKey, environment?: "mainnet" | "devnet", connection?: Connection)
ParameterTypeDefaultDescription
mintPublicKey—The tokenized agent's token mint address
environment"mainnet" | "devnet""mainnet"Network environment
connectionConnection (optional)undefinedSolana RPC connection (enables RPC fallback for verification)

Without connection — enough for building instructions and HTTP-based payment verification:

typescript
const agent = new PumpAgent(agentMint);

With connection — also enables RPC-based verification fallback and balance queries:

typescript
import { Connection } from "@solana/web3.js";

const connection = new Connection(process.env.SOLANA_RPC_URL!);
const agent = new PumpAgent(agentMint, "mainnet", connection);

Wallet Integration (Frontend)

Install @solana/wallet-adapter-react, @solana/wallet-adapter-react-ui, and @solana/wallet-adapter-wallets. Use useWallet() for publicKey and signTransaction, and useConnection() for the active RPC connection. MUST See https://raw.githubusercontent.com/pump-fun/pump-fun-skills/refs/heads/main/tokenized-agents/references/WALLET_INTEGRATION.md for the full WalletProvider setup, layout wrapping, and hook usage.

Building Payment Instructions

Use buildAcceptPaymentInstructions to get all the instructions needed for a payment. This is the recommended method — it automatically derives the user's token account and handles native SOL wrapping/unwrapping.

Parameters (BuildAcceptPaymentParams)
ParameterTypeDescription
userPublicKeyThe payer's wallet address
currencyMintPublicKeyMint address of the payment currency (USDC, wSOL)
amountbigint | number | stringPrice in the currency's smallest unit
memobigint | number | stringUnique invoice identifier (random number)
startTimebigint | number | stringUnix timestamp — when the invoice becomes valid
endTimebigint | number | stringUnix timestamp — when the invoice expires
tokenProgramPublicKey (optional)Token program for the currency (defaults to SPL Token)
computeUnitLimitnumber (optional)Compute unit budget (default 100_000). Increase if transactions fail with compute exceeded.
computeUnitPricenumber (optional)Priority fee in microlamports per CU. If provided, a SetComputeUnitPrice instruction is prepended.
Example
typescript
const ixs = await agent.buildAcceptPaymentInstructions({
  user: userPublicKey,
  currencyMint,
  amount: "1000000", // 1 USDC
  memo: "123456789", // unique invoice identifier
  startTime: "1700000000", // valid from
  endTime: "1700086400", // expires at
});
What It Returns

The returned TransactionInstruction[] always starts with compute budget instructions, followed by the payment instructions:

  • SetComputeUnitLimit is always prepended (default 92_849 CU). Override via computeUnitLimit if your transactions fail with "compute exceeded".
  • SetComputeUnitPrice is prepended only when computeUnitPrice is provided. Use this to set a priority fee for faster landing during congestion.

After the compute budget prefix:

  • For SPL tokens (USDC): The accept-payment instruction.
  • For native SOL: Instructions that handle wrapping/unwrapping automatically:
    1. Create the user's wrapped SOL token account (idempotent)
    2. Transfer SOL lamports into that token account
    3. Sync the native balance
    4. The accept-payment instruction
    5. Close the wrapped SOL account (returns rent back to user)

You do not need to handle SOL wrapping or compute budget yourself — buildAcceptPaymentInstructions does it for you.

Show full SKILL.md (429 more words)Show less
Important
  • The amount, memo, startTime, and endTime must exactly match when verifying later.
  • Each unique combination of (mint, currencyMint, amount, memo, startTime, endTime) can only be paid once — the on-chain Invoice ID PDA prevents duplicate payments.
  • Generate a unique memo for each invoice (e.g. Math.floor(Math.random() * 900000000000) + 100000).

Full Transaction Flow — Server to Client

This is the complete flow for building a transaction on the server, signing it on the client, and sending it on-chain.

Step 1: Generate Invoice Parameters (Server)
typescript
function generateInvoiceParams() {
  const memo = String(Math.floor(Math.random() * 900000000000) + 100000);
  const now = Math.floor(Date.now() / 1000);
  const startTime = String(now);
  const endTime = String(now + 86400); // valid for 24 hours
  const amount = process.env.PRICE_AMOUNT || "1000000"; // e.g. 1 USDC

  return { amount, memo, startTime, endTime };
}
Step 2: Build Transaction and Serialize as Base64 (Server)

Build the payment instructions, assemble them into a full Transaction with a recent blockhash and fee payer, then serialize the unsigned transaction as a base64 string for the client.

typescript
import {
  Connection,
  PublicKey,
  Transaction,
  ComputeBudgetProgram,
} from "@solana/web3.js";
import { PumpAgent } from "@pump-fun/agent-payments-sdk";

async function buildPaymentTransaction(params: {
  userWallet: string;
  amount: string;
  memo: string;
  startTime: string;
  endTime: string;
}) {
  const connection = new Connection(process.env.SOLANA_RPC_URL!);
  const agentMint = new PublicKey(process.env.AGENT_TOKEN_MINT_ADDRESS!);
  const currencyMint = new PublicKey(process.env.CURRENCY_MINT!);

  const agent = new PumpAgent(agentMint, "mainnet", connection);
  const userPublicKey = new PublicKey(params.userWallet);

  const instructions = await agent.buildAcceptPaymentInstructions({
    user: userPublicKey,
    currencyMint,
    amount: params.amount,
    memo: params.memo,
    startTime: params.startTime,
    endTime: params.endTime,
  });

  const { blockhash } = await connection.getLatestBlockhash("confirmed");

  const tx = new Transaction();
  tx.recentBlockhash = blockhash;
  tx.feePayer = userPublicKey;
  tx.add(
    ComputeBudgetProgram.setComputeUnitPrice({ microLamports: 100_000 }),
    ...instructions,
  );

  const serializedTx = tx
    .serialize({ requireAllSignatures: false })
    .toString("base64");

  return { transaction: serializedTx };
}

Return the base64 transaction string (and the invoice params like memo, startTime, endTime) to the client as JSON.

Step 3: Deserialize, Sign, and Send the Transaction (Client)

Deserialize the base64 transaction from the server, sign it with signTransaction from the wallet adapter, then send and confirm it. Call useWallet() and useConnection() only at the top level of your component; pass signTransaction and connection into the async helper so the async logic does not call hooks.

Async helper (e.g. in a utils file or alongside your component):

typescript
import { Connection, Transaction } from "@solana/web3.js";

async function signAndSendPayment(
  txBase64: string,
  signTransaction: (tx: Transaction) => Promise<Transaction>,
  connection: Connection,
): Promise<string> {
  if (!signTransaction) {
    throw new Error("Wallet does not support signing");
  }

  const tx = Transaction.from(Buffer.from(txBase64, "base64"));
  const signedTx = await signTransaction(tx);

  const signature = await connection.sendRawTransaction(signedTx.serialize(), {
    skipPreflight: false,
    preflightCommitment: "confirmed",
  });

  const latestBlockhash = await connection.getLatestBlockhash("confirmed");
  await connection.confirmTransaction(
    { signature, ...latestBlockhash },
    "confirmed",
  );

  return signature;
}

Component usage — call the hooks at the top level, then pass them into the helper (e.g. from a payment button handler):

typescript
import { useWallet, useConnection } from "@solana/wallet-adapter-react";

function PaymentButton({ txBase64 }: { txBase64: string }) {
  const { signTransaction } = useWallet();
  const { connection } = useConnection();

  const handlePay = async () => {
    if (!signTransaction) return;
    await signAndSendPayment(txBase64, signTransaction, connection);
  };

  return <button onClick={handlePay}>Pay</button>;
}

The wallet prompts the user to approve. After signing, the serialized transaction is submitted via sendRawTransaction and you wait for on-chain confirmation.

Verify Payment

Use validateInvoicePayment to confirm that a specific invoice was paid on-chain.

How It Works
  1. Derives the Invoice ID PDA from (mint, currencyMint, amount, memo, startTime, endTime).
  2. Queries the Pump HTTP API to check if the payment event exists.
  3. If the HTTP API is unavailable and a Connection was provided, falls back to scanning on-chain transaction logs via RPC.
  4. Returns true if a matching payment event is found, false otherwise.
Parameters
ParameterTypeDescription
userPublicKeyThe wallet that paid
currencyMintPublicKeyCurrency used for payment
amountnumberAmount paid (smallest unit)
memonumberThe invoice memo
startTimenumberInvoice start time (Unix timestamp)
endTimenumberInvoice end time (Unix timestamp)
Simple Backend Verification
typescript
import { PumpAgent } from "@pump-fun/agent-payments-sdk";
import { PublicKey } from "@solana/web3.js";

const agentMint = new PublicKey(process.env.AGENT_TOKEN_MINT_ADDRESS!);
const agent = new PumpAgent(agentMint);

const paid = await agent.validateInvoicePayment({
  user: new PublicKey(userWalletAddress),
  currencyMint: new PublicKey(process.env.CURRENCY_MINT!),
  amount: 1000000,
  memo: 123456789,
  startTime: 1700000000,
  endTime: 1700086400,
});

if (paid) {
  // Payment confirmed — deliver the service
} else {
  // Payment not found
}

No Connection is needed for basic verification — it uses the HTTP API by default.

Verification with Retries

Transactions may take a few seconds to confirm. Use a retry loop for reliability:

typescript
async function verifyPayment(params: {
  user: string;
  currencyMint: string;
  amount: number;
  memo: number;
  startTime: number;
  endTime: number;
}): Promise<boolean> {
  const agentMint = new PublicKey(process.env.AGENT_TOKEN_MINT_ADDRESS!);
  const agent = new PumpAgent(agentMint);

  const invoiceParams = {
    user: new PublicKey(params.user),
    currencyMint: new PublicKey(params.currencyMint),
    amount: params.amount,
    memo: params.memo,
    startTime: params.startTime,
    endTime: params.endTime,
  };

  for (let attempt = 0; attempt < 10; attempt++) {
    const verified = await agent.validateInvoicePayment(invoiceParams);
    if (verified) return true;
    await new Promise((r) => setTimeout(r, 2000));
  }

  return false;
}

End-to-End Flow

1. Agent decides on price → generates unique memo → sets time window
       ↓
2. Server: buildAcceptPaymentInstructions(...) → returns TransactionInstruction[]
       ↓
3. Server: builds full Transaction (blockhash + feePayer + instructions) → serializes as base64
       ↓
4. Client: deserializes base64 → Transaction.from(Buffer.from(txBase64, "base64"))
       ↓
5. Client: signTransaction(tx) — wallet prompts user to approve
       ↓
6. Client: connection.sendRawTransaction(signedTx.serialize()) → connection.confirmTransaction(signature)
       ↓
7. Server: validateInvoicePayment(...) → returns true/false (ALWAYS verify server-side)
       ↓
8. Agent delivers the service (or asks user to retry)

Scenario Tests & Troubleshooting

See https://raw.githubusercontent.com/pump-fun/pump-fun-skills/refs/heads/main/tokenized-agents/references/SCENARIOS.md for detailed test scenarios (happy path, duplicate rejection, expired invoices, etc.) and a troubleshooting table for common errors and for wallet Integration must follow https://raw.githubusercontent.com/pump-fun/pump-fun-skills/refs/heads/main/tokenized-agents/references/WALLET_INTEGRATION.md.

© LeoYeAI, 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 3 other files (references) in skills/pump-fun-tokenized-agents of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • references/SCENARIOS.md
  • references/WALLET_INTEGRATION.md

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Tokenized Agents 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.

Tokenized Agents compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tokenized Agents this skillLeoYeAI/openclaw-master-skills2.2k—~4.6kAutomated safety check: NotesMIT
Alchemy Agentic Gatewaymoonpay/skills113—~2.1kAutomated safety check: NotesMIT
Payram Crypto PaymentsPayRam/payram-mcp158—~2kAutomated safety check: NotesNone
Swap Tokenscirclefin/skills155—~4.6kAutomated safety check: NotesApache-2.0
Unify Balancecirclefin/skills155—~4.7kAutomated safety check: NotesApache-2.0
Use Usdccirclefin/skills155—~2.4kAutomated safety check: NotesApache-2.0

Similar skills

  • A skill your agent uses when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features.

    113 GitHub stars~2.1k tokensUpdated 28 days ago
    Backend & APIsAuto-check: notes
  • Payram Crypto Payments

    PayRam/payram-mcp

    Self-hosted crypto and stablecoin payment gateway. An agent skill from PayRam/payram-mcp.

    158 GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check: notes
  • Swap Tokens

    circlefin/skills

    Build browser or server token swaps with Circle App Kit or standalone Swap Kit.

    155 GitHub stars~4.6k tokensUpdated 22 days ago
    Backend & APIsAuto-check: notes
  • Unify Balance

    circlefin/skills

    Build browser or server unified cross-chain USDC balances with Circle App Kit or standalone Unified Balance Kit.

    155 GitHub stars~4.7k tokensUpdated 22 days ago
    Backend & APIsAuto-check: notes
  • Use Usdc

    circlefin/skills

    USDC is Circle's stablecoin deployed across multiple blockchain ecosystems including EVM chains (Ethereum, Base, Arbitrum, Polygon, Arc) and Solana.

    155 GitHub stars~2.4k tokensUpdated 22 days ago
    Backend & APIsAuto-check: notes
  • Build non-custodial wallets where end users retain control of their private keys via Circle's user-controlled wallets SDK.

    155 GitHub stars~3.6k tokensUpdated 22 days ago
    Backend & APIsAuto-check: notes

More from LeoYeAI/openclaw-master-skills

All 972 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Tokenized Agents

What does Tokenized Agents do?

Build payment flows for Pump Tokenized Agents using @pump-fun/agent-payments-sdk. Tokenized Agents is an agent skill from LeoYeAI/openclaw-master-skills. Build payment flows for Pump Tokenized Agents using @pump-fun/agent-payments-sdk.

When should I use Tokenized Agents?

Tokenized Agents fits situations like: accepting payments; building accept-payment transactions; integrating Solana wallets; verifying that a user has paid an invoice on-chain.

How do I install Tokenized Agents in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill tokenized-agents -a claude-code`. Or copy the skill folder (skills/pump-fun-tokenized-agents in LeoYeAI/openclaw-master-skills) into .claude/skills/tokenized-agents in your project. Claude Code loads it when a task matches its description.

How do I install Tokenized Agents in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill tokenized-agents -a codex`. Or copy the skill folder (skills/pump-fun-tokenized-agents in LeoYeAI/openclaw-master-skills) into .agents/skills/tokenized-agents in your project. Codex loads it when a task matches its description.

Can I use Tokenized Agents 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 LeoYeAI/openclaw-master-skills --skill tokenized-agents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tokenized-agents, .gemini/skills/tokenized-agents, .github/skills/tokenized-agents and .opencode/skills/tokenized-agents in your project.

What does Tokenized Agents need to run?

Going by SKILL.md and its folder, Tokenized Agents needs the command-line tools its instructions call (npm). Our summary lists: Node.js.

Does Tokenized Agents access the network?

SKILL.md names 4 domains. In commands or code: rpc.solanatracker.io, api.mainnet-beta.solana.com and rpc.ankr.com; the agent is likely to contact these when it follows the instructions. As links in the text: raw.githubusercontent.com. This is read from the text; nothing was executed.

Is Tokenized Agents safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Tokenized Agents use?

Tokenized Agents is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tokenized Agents use?

About 4.6k tokens (SKILL.md is roughly 18k 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 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Tokenized Agents?

Skills that share tags, products or a category with Tokenized Agents: Alchemy Agentic Gateway (moonpay/skills, 113 stars), Payram Crypto Payments (PayRam/payram-mcp, 158 stars), Swap Tokens (circlefin/skills, 155 stars) and Unify Balance (circlefin/skills, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tokenized Agents?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.