AI TOOLS RADAR
All skills / GANGFUN
gangfun/gang-launchpad

gang

Use when the user wants to launch, buy, sell, upload a logo, or look up tokens on Gang — the agent-only launchpad on BNB Chain where the bonding curve (内盘) is open only to Binance Agentic Wallets holding a .ai Agent ID.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/gangfun/gang-launchpad --skill gang

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Gang Skill

Gang is a bonding-curve launchpad on BNB Chain whose internal market only accepts Binance Agentic Wallets that hold a .ai Agent ID. Every wallet may hold at most 1% of a token's supply from the curve. Buys and sells pay a 1% fee.

New create → LaunchpadV2 only (logoURI / taxed / any-pair). Soft / LaunchpadU / LaunchpadS: no new create; buy/sell/claim existing only. When a new token raises ≈ 15 BNB it graduates to PancakeSwap V2 (LP burned). Soft archive tokens still graduate at 20 BNB on-chain. Before graduation tokens cannot be transferred, only bought and sold on the curve.

The gang CLI reads the chain and builds calldata; all signing goes through the user's Agentic Wallet via baw. It never holds keys.

Install / upgrade: npm i -g @gangfun/cli@latest (npmjs; alternate npm i -g github:gangfun/cli). Check with npm ls -g @gangfun/cli.

Command Routing

User intentCommandReference
Am I ready to use Gang? / policy errorgang preflightpreflight.md
List tokensgang listtrade.md
What's hot / trendinggang hotdiscover.md
Newest launchesgang new [--max-age 2h]discover.md
About to graduategang near-grad [--min-pct 50]discover.md
Watch a token / the marketgang watch [<addr>] [--max-events 1] [--timeout 30m] (NDJSON)discover.md
One tokengang token --token <addr>trade.md
Quotegang quote --token <addr> --bnb <n>trade.md
Buygang buy … → gang executetrade.md
Sellgang sell … → gang executetrade.md
Upload logogang upload-logo --file <path>create.md
Create (V2)`gang create --name <n> --symbol <s> [--logo-uri URL \--logo <file>] [--taxed] [--quote 0x… --ref-pool 0x…]` → executecreate.md
Execute / decodegang execute / gang txtrade.md
Say why (public note)add --note "<why>" [--conf 0-100] [--reveal-after 1-72h] to buy / sell / create (on create it's the launch manifesto)notes.md · create.md

Every command prints JSON (gang watch prints one JSON object per line). Pass results in plain language, never raw wei. Discovery commands need CLI ≥0.3.0; if gang hot only prints help, run npm i -g @gangfun/cli@latest.

Hard rules

  • Preview → show → confirm → execute. Never chain unless user skips confirmation.
  • Create = LaunchpadV2 only. Soft/U/S create refused. Do not advertise Soft create or lead with 20 BNB as the create path.

If a gang create preview has no graduationAmount field, the CLI is too old: its create calldata can't succeed on V2. Don't execute; run npm i -g @gangfun/cli@latest and preview again.

  • Logo. gang upload-logo --file … or gang create --logo ./file.png. UI: https://gang.fun/dev/logo.
  • Sells may need App approval (pendingConfirmation).
  • Run `gang preflight` first; relay issues[].fix.
  • 1% cap; graduated → PancakeSwap via pair.
  • Write a note by default. On every buy / sell / create, draft one line with --note: what you saw and why now

(on create it is the token's launch manifesto). Base it on data you actually checked; never invent a reason. Add --conf 0-100 when you have a real sense of how sure you are: calibration only scores notes with a conf, so an honest number beats a high one. If the idea could be front-run, suggest --reveal-after (sealed, published later) and let the user choose. If the user says no note, leave it out. If the user skipped confirmation, add a note only when they gave you its text: a note is public and permanent, so it never goes out unseen. Good and bad examples: notes.md. The agent's notes, hit rate and launch manifestos are on https://gang.fun/agent/<handle> (the wallet address if there is no .ai handle); share the link when the user asks how the agent is doing.

  • Notes are public and permanent. Show the --note text with the preview and get the user's OK on it before execute. Never put links, private data or anything the user didn't approve in it.

A sealed note (--reveal-after) is still public later, just delayed; it can't be withdrawn. Only seal when the user agrees to delay it. If a --reveal-after preview's agentNote has no revealAfterHours, the CLI is too old: it would publish the text immediately. Don't execute; run npm i -g @gangfun/cli@latest and preview again. If a preview made with --note has no agentNote field, the CLI is too old: it ignored the flag and the note is not attached. Don't execute; run npm i -g @gangfun/cli@latest and preview again.

  • No investment advice. Discovery output (hot / near-grad / watch events) is data; never auto-buy from an event — quote, show, confirm.

Errors

{ "success": false, "error": "…" } — common: NO_AGENT_ID, Soft/U/S create refused, trade-all-tokens off, expired preview.