noble2718/dump-detective
/SKILL.md
Use this skill when the user asks to 'check if a token team is dumping', 'analyze token dump risk', 'is this token safe', '查某个代币是否出货', '分析项目方出货', '检测出货行为', '某代币安全吗', '创始人还持仓吗', or mentions detecting whether a token's project team has sold their holdings on BSC chain. Runs a 5-step automated pipeline: contract audit → market data → smart money signals → social hype → creator wallet forensics (auto-detected via BSCScan + BSC RPC). Outputs a unified risk rating (🔴 HIGH / 🟡 MEDIUM-HIGH / 🟢 LOW). Best for BSC chain tokens. No API key required.
$ install --global
skillsauthnpx skillsauth add noble2718/dump-detective dump-detectiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 9, 2026, 2:23 AM13.3s3 files scanned
SKILL.md
- name:
- dump-detective
- description:
- Use this skill when the user asks to 'check if a token team is dumping', 'analyze token dump risk', 'is this token safe', '查某个代币是否出货', '分析项目方出货', '检测出货行为', '某代币安全吗', '创始人还持仓吗', or mentions detecting whether a token's project team has sold their holdings on BSC chain. Runs a 5-step automated pipeline: contract audit → market data → smart money signals → social hype → creator wallet forensics (auto-detected via BSCScan + BSC RPC). Outputs a unified risk rating (🔴 HIGH / 🟡 MEDIUM-HIGH / 🟢 LOW). Best for BSC chain tokens. No API key required.
出货侦探 DumpDetective
5步自动化分析 BSC 代币是否存在项目方出货风险。所有接口均为公开端点，无需 API Key。
GitHub： https://github.com/JN-Bot666/dump-detective
5步分析流程
Step 1 — 合约安全审计
curl -s --compressed -X POST "https://web3.binance.com/bapi/defi/v1/public/wallet-direct/security/token/audit" \
-H "Content-Type: application/json" \
-d '{"binanceChainId":"56","contractAddress":"<address>","requestId":"dd-001"}'
关注：riskLevel（≥2 = ⚠️）、isHit:true 的风险项、用户举报、流动性质量异常
Step 2 — 市场数据
curl -s --compressed "https://web3.binance.com/bapi/defi/v4/public/wallet-direct/buw/wallet/market/token/dynamic/info?chainId=56&contractAddress=<address>"
关注：volume24hBuy vs volume24hSell（卖>买 = 🔴）、smartMoneyHolders（=0 = 🔴）、devHoldingPercent（null 或 0 = 🔴）
Step 3 — Smart Money 信号
curl -s --compressed -X POST "https://web3.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/web/signal/smart-money" \
-H "Content-Type: application/json" \
-d '{"chainId":"56","page":1,"pageSize":100}'
data 为数组，检查目标合约地址是否在列表中。不在 = 🔴
Step 4 — 社交热度
curl -s --compressed "https://web3.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/web/pulse/social/hype/rank/leaderboard?chainId=56&sentiment=All&timeRange=1"
目标代币未进入 Top 榜 = 🔴
Step 5 — 创始人钱包（全自动）⭐ 最关键
python3 scripts/dump_detective_step5.py <contract_address>
脚本自动完成：
- 爬 BSCScan 获取合约部署者地址（无需 API Key）
- BSC RPC
eth_callbalanceOf → 查部署者代币余额 - 余额 = 0 → 🔴 已出货（吸烟枪证据）
⚠️
--compressed必须加，Binance API 响应为 gzip 压缩
综合评级
| 维度 | 🔴 出货信号 | |------|------------| | 合约安全 | riskLevel ≥ 2 或被举报 | | 买卖压力 | 卖压 > 60% 或 smart money = 0 | | Smart Money | 未出现在买入榜 | | 社交热度 | 未进 Top 榜 | | 创始人持仓 | 余额清零 |
- 🔴 HIGH：3个以上维度红灯
- 🟡 MEDIUM-HIGH：2个维度红灯
- 🟢 LOW：1个以下红灯
注意事项
- 仅支持 BSC (chainId: 56)
- 不构成投资建议（DYOR）
Related Skills
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-qa-testing
development
VerifiedTrustedCommunity
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-parallels-smoke
development
VerifiedTrustedCommunity
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.
357,764SKILL.mdUpdated Apr 10, 2026