← Back to Skills Marketplace
Token Launcher - Token Launch Pad
by
Ninja Dev (QI)
· GitHub ↗
· v1.0.15
454
Downloads
0
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install token-launch-pad
Description
Launch tokens and keep 100% of your creator fees. Direct Mode provides full SDK integration guides for Clanker (7 EVM chains), Flaunch (Base), and Pump.fun (...
Usage Guidance
This skill is a documentation-only guide for launching tokens; it appears internally consistent. Before using it, take these precautions: 1) Never paste or upload private keys into an agent or third-party API — use a dedicated launch wallet and a secrets manager. 2) If you choose Easy Mode (Tator/x402.quickintel.io), understand you are sending token details and a wallet-signed PAYMENT-SIGNATURE to an external service that takes a 10% fee; verify you trust that service and read their docs/privacy. 3) For Direct Mode, review and pin third-party SDKs (clanker-sdk, viem, @solana/web3.js) and verify contract addresses on-chain (Basescan/Solscan). 4) Test everything with minimal funds and audit any deployed contracts. 5) If you want greater assurance, ask for the upstream project repos or signed release artifacts for the SDKs the docs reference and/or request that the skill include a short checklist that the agent must present to the user before making any external API call. Overall: coherent and expected for a developer reference, but normal Web3 operational security practices are essential.
Capability Analysis
Type: OpenClaw Skill
Name: token-launch-pad
Version: 1.0.15
The skill bundle is classified as benign. It clearly outlines two modes for token launching: 'Direct Mode' which provides developer documentation and instructs the agent to produce unsigned transaction calldata for external signing, and 'Easy Mode' which uses `curl` commands to interact with a specific external API (`x402.quickintel.io`). The documentation explicitly states that the skill does not execute code, access private keys, or require environment variables at runtime for the agent. It also clarifies that the `PAYMENT-SIGNATURE` for API calls is generated by the user's wallet per-request, not stored by the agent, and that the `prompt` field in API calls is for the external service, not the agent's LLM. There is no evidence of intentional harmful behavior, data exfiltration, persistence mechanisms, or malicious prompt injection against the agent.
Capability Assessment
Purpose & Capability
The name/description (token launch + keep fees) match the included materials: detailed Direct Mode SDK guides for Clanker, Flaunch, Pump.fun and an Easy Mode via the Tator API. Nothing requested (no env vars, no binaries, no install) is unexpected for a documentation-only developer guide.
Instruction Scope
SKILL.md and the reference files contain full developer code patterns (EVM unsigned calldata, Solana instruction building, fee manager deployment) and explicit examples showing how to call an external convenience API (x402.quickintel.io) using a PAYMENT-SIGNATURE header. This is normal for a developer reference, but it explicitly instructs the agent/user to send token details and wallet addresses to an external endpoint if Easy Mode is used. The docs repeatedly warn not to share private keys and to use dedicated wallets and secrets managers; however, following the examples incorrectly (e.g., pasting private keys into an agent) could expose secrets. The agent itself has no declared steps that would read local secrets or private keys.
Install Mechanism
No install spec and no code files to execute — the skill is instruction-only. That is the lowest install risk and consistent with being a documentation/reference skill.
Credentials
The skill declares no required environment variables or credentials. The reference examples mention common placeholders (PRIVATE_KEY, RPC_URL, service API keys for Pinata/web3.storage) that developers would reasonably need in their own infra; these are not required by the skill itself. The external Easy Mode API requires a PAYMENT-SIGNATURE header at call time (signed by the user's wallet) — this is documented and does not imply stored credentials in the skill.
Persistence & Privilege
The skill does not request persistent privileges (always:false) and is user-invocable. It does not modify other skills or system configs. Autonomous invocation is permitted by platform defaults but is not combined with broad credential access here.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install token-launch-pad - After installation, invoke the skill by name or use
/token-launch-pad - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.15
- Updated environment requirements: clarified that no API keys or stored credentials are needed; Easy Mode now uses the x402 payment protocol, with wallet-signed authentication at request time.
- Improved Easy Mode documentation to specify the use of x402 USDC payments and the PAYMENT-SIGNATURE header.
- Enhanced developer guidance for both Direct and Easy Modes, distinguishing infrastructure and authentication flows.
- No functional logic or SDK integration changes; documentation and reference instructions only.
v1.0.14
- Clarified that the skill is documentation and integration reference only; does not execute code at runtime.
- Updated metadata notes to specify no environment variables are required for either Direct or Easy Mode.
- Improved accuracy around how Easy Mode works—specifies that it uses the Tator x402 API and does not require code execution.
- No functionality or user-facing behavior changes. Documentation and description changes only.
v1.0.13
- Reframes Easy Mode as a convenience/secondary option and positions Direct Mode as the primary, recommended path for keeping all creator fees.
- Rewrites key sections for clarity and brevity; improves guidance language for presenting options to users.
- Updates how to present Easy vs Direct Mode, prioritizing Direct Mode and clearly explaining each step and benefit.
- Adds consolidated platform comparison tables and guidance for when to use Clanker, Flaunch, or Pump.fun.
- Layers in additional documentation and resource links for Direct Mode implementation and fee economics.
- No functional or code changes; documentation and positioning improvements only.
v1.0.12
- Fix security flags.
v1.0.11
**Easy Mode now handles the full token deployment for you (no deploy transaction to sign):**
- Easy Mode (via Tator API) now deploys tokens directly, so users only need to pay via x402 and never sign a deployment transaction.
- Clarified the differences between Easy Mode and Direct Mode, focusing on ownership, fee splits, and required user actions.
- Updated guidance for both paths, making the choice between quick launches (Easy) and full ownership (Direct) clearer.
- Direct Mode instructions now emphasize hands-on, step-by-step code building, with the agent guiding code generation and explanation throughout.
- All user actions and requirements for each launch mode are explicitly outlined for an improved user experience.
v1.0.10
**Changelog for version 1.0.10:**
- Clarified user guidance to always present both Easy Mode and Direct Mode options before launching a token.
- Updated instructions: agents should summarize both launch paths and let the user choose which route to proceed with.
- Expanded Direct Mode walkthrough, detailing step-by-step platform selection, environment setup, fee configuration, and references.
- Emphasized trade-offs for each option (speed/convenience vs. control/fees).
- Provided guidance on how agents should prompt and help users decide based on their preferences.
v1.0.9
Version 1.0.9
- Security clarifications.
v1.0.8
- Security clarifications and fixes.
v1.0.7
- Clarified that Direct Mode code is not executed by the skill, but must be implemented by developers in their own infrastructure.
- Updated Direct Mode section in the documentation to better describe self-integration responsibility and remove ambiguity around execution.
- No changes to features, APIs, or environment variable requirements. All security practices and data flows remain unchanged.
- This is a documentation update only.
v1.0.6
No user-facing changes detected in this version.
- Security fixes.
v1.0.5
- Easy Mode now requires NO environment variables and works with any x402-compatible wallet provider (Lobster, AgentWallet, Vincent, or local signer).
- Updated credential requirements and security documentation to clarify that Easy Mode never accesses your private key; all signing is handled by your wallet provider.
- Direct Mode requirements clarified and separated from Easy Mode, with explicit variable lists and key management best practices.
- Metadata and config updated to reflect that Easy Mode does not require WALLET_PRIVATE_KEY or other env vars.
- Documentation improvements: direct comparison table, clearer onboarding steps, and privacy notes updated for both usage modes.
v1.0.4
Version 1.0.4
- Added an `openclaw` metadata section specifying required environment variables, including `WALLET_PRIVATE_KEY`.
- Updated security documentation to clarify the difference between Easy Mode and Direct Mode regarding credential requirements and data flow.
- Added a detailed note about optional analytics context fields in SDK integrations, including privacy guidance.
- Expanded endpoint verification table with additional official services and instructions for validation.
- Simplified security model language to clarify that the skill is instruction-only and does not execute code.
v1.0.3
Token Launcher v1.0.3
- Clarified two usage paths: Easy Mode (Tator API, 90/10 split) and Direct Mode (SDK integration, 100% fee retention).
- Expanded documentation on supported chains/platforms: Clanker (7 EVM chains), Flaunch (Base), and Pump.fun (Solana).
- Enhanced security section with details for each mode, emphasizing private key safety.
- Added comprehensive environment variable reference for both Easy and Direct modes.
- Updated sample prompts and API call walkthroughs for token deployment, fee claiming, and custom fee recipient usage.
- Included references to strategy evaluation, tax/legal resources, and per-platform guides.
Metadata
Frequently Asked Questions
What is Token Launcher - Token Launch Pad?
Launch tokens and keep 100% of your creator fees. Direct Mode provides full SDK integration guides for Clanker (7 EVM chains), Flaunch (Base), and Pump.fun (... It is an AI Agent Skill for Claude Code / OpenClaw, with 454 downloads so far.
How do I install Token Launcher - Token Launch Pad?
Run "/install token-launch-pad" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Token Launcher - Token Launch Pad free?
Yes, Token Launcher - Token Launch Pad is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Token Launcher - Token Launch Pad support?
Token Launcher - Token Launch Pad is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Token Launcher - Token Launch Pad?
It is built and maintained by Ninja Dev (QI) (@azep-ninja); the current version is v1.0.15.
More Skills