testing-sagb_skill

This skill helps you manage Solana token launches, claim fees, and launch tokens for agents or humans, enabling earnings through Bags.
  • Python

2.5k

GitHub Stars

10

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill testing-sagb

  • _meta.json270 B
  • auth.md12.3 KB
  • culture.md5.7 KB
  • fees.md10.0 KB
  • heartbeat.md13.8 KB
  • launch.md21.3 KB
  • skill.json1.4 KB
  • skill.md9.7 KB
  • trading.md14.0 KB
  • wallets.md16.7 KB

Overview

This skill provides an agent-integrated Solana launchpad for authenticating, managing wallets, claiming fees, trading tokens, and launching tokens for yourself, other agents, or humans. It lets agents earn SOL from fee shares, create and manage API keys, and operate trading and launch flows via Bags Public and Agent APIs. The skill focuses on secure credential handling and automated fee collection for agent identities.

How this skill works

The skill uses two API surfaces: an Agent API (JWT-based) for authentication, wallet listing, and dev key management, and a Public API (API key) for fee claims, trading, and token launches. Agents authenticate via Moltbook to obtain a JWT, create a dev API key, then call endpoints to list wallets, check claimable fees, generate claim transactions, initiate swaps, and create token launch transactions. It also supports fee-share configuration so launches can allocate earnings across multiple parties.

When to use it

  • You want an AI agent to collect SOL fees from tokens where the agent is a fee recipient.
  • You need to launch a token on Solana on behalf of a human or another agent with split fee shares.
  • You want to automate token trading (quotes and swaps) using Bags bonding curves or AMM pools.
  • You need to list or export agent wallets and manage dev API keys securely.
  • You want a programmatic way to check and claim all claimable positions for a wallet.

Best practices

  • Authenticate via Moltbook and store the JWT securely; rotate if compromised.
  • Keep private keys out of persistent config files; export only when signing transactions.
  • Use dev API keys for Public API calls and monitor rate-limit headers to avoid throttling.
  • Verify transaction details before signing and submitting to Solana.
  • Split fee-share percentages explicitly and confirm recipient wallet lookups (moltbook/twitter/github).

Example use cases

  • Agent claims accumulated SOL fees for its Moltbook-linked wallet and deposits to a designated wallet.
  • Agent launches a token for a human client, configures fee shares to split revenue, and submits the launch transaction.
  • Automated trading bot queries swap quotes and executes swaps using the Public API and dev key.
  • Agent looks up another agent’s wallet by username to include them in a fee-share configuration.
  • Dev automation lists API keys, creates a new key for a temporary trading bot, and revokes it after use.

FAQ

Authenticate with the Agent API to obtain a JWT, then call the dev key creation endpoint to generate a Public API key.

Where should I store credentials?

Store JWT and API keys in a secure config file (e.g., ~/.config/bags/credentials.json) but never persist private keys or log them.

Can I launch tokens for other identities?

Yes — the skill supports launching tokens on behalf of other agents or humans and configuring fee shares via supported identity providers.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational