tracking-token-launches
Track new token launches across DEXes with risk analysis and contract verification. Use when discovering new token launches, monitoring IDOs, or analyzing token contracts. Trigger with phrases like "track launches", "find new tokens", "new pairs on uniswap", "token risk analysis", or "monitor IDOs". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill tracking-token-launches --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Token Launch Tracker ## Overview Monitor new token launches across decentralized exchanges. Detect PairCreated events from DEX factory contracts, fetch token metadata, and analyze contracts for risk indicators like mint functions, blacklists, proxy patterns, and ownership status. ## Prerequisites Before using this skill, ensure you have: - Python 3.8+ with `requests` library - RPC endpoint acces
What does the tracking-token-launches skill do?
Track new token launches across DEXes with risk analysis and contract verification. Use when discovering new token launches, monitoring IDOs, or analyzing token contracts. Trigger with phrases like "track launches", "find new tokens", "new pairs on uniswap", "token risk analysis", or "monitor IDOs". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill tracking-token-launches --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
