okx-dex-trenches by okx/onchainos-skills
npx skills add https://github.com/okx/onchainos-skills --skill okx-dex-trenches7 个用于迷因代币发现、开发者分析、捆绑检测和同车追踪的命令。
每次运行任何 onchainos 命令之前,请始终按顺序遵循以下步骤。不要向用户回显常规命令输出;仅在安装、更新或处理失败时提供简短的状态更新。
解析最新稳定版本 :从 GitHub API 获取最新的稳定发布标签:
curl -sSL "https://api.github.com/repos/okx/onchainos-skills/releases/latest"
将 tag_name 字段(例如 v1.0.5)提取到 LATEST_TAG 中。如果 API 调用失败且 onchainos 已本地安装,则跳过步骤 2-3 并继续运行命令(用户可能离线或被限速;过时的二进制文件总比阻塞好)。如果 onchainos 未安装,则停止并告知用户检查网络连接或从 https://github.com/okx/onchainos-skills 手动安装。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
onchainos,或者位于 ~/.onchainos/last_check(Windows 上为 $env:USERPROFILE\.onchainos\last_check)的缓存超过 12 小时: * 从最新的发布标签下载安装程序及其校验和文件:
* **macOS/Linux** : `curl -sSL "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.sh" -o /tmp/onchainos-install.sh` `curl -sSL "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -o /tmp/installer-checksums.txt`
* **Windows** : `Invoke-WebRequest -Uri "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.ps1" -OutFile "$env:TEMP\onchainos-install.ps1"` `Invoke-WebRequest -Uri "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -OutFile "$env:TEMP\installer-checksums.txt"`
* 根据 `installer-checksums.txt` 验证安装程序的 SHA256。如果不匹配,**停止**并发出警告——安装程序可能已被篡改。
* 执行:`sh /tmp/onchainos-install.sh`(或在 Windows 上执行 `& "$env:TEMP\onchainos-install.ps1"`)。安装程序内部处理版本比较,仅在需要时下载二进制文件。
* 对于其他失败情况,请指向 <https://github.com/okx/onchainos-skills>。
3. 验证二进制文件完整性(每个会话一次):运行 onchainos --version 获取已安装版本(例如 1.0.5 或 2.0.0-beta.0)。将已安装的标签构造为 v<version>。下载已安装版本标签(不一定是 LATEST_TAG)的 checksums.txt:curl -sSL "https://github.com/okx/onchainos-skills/releases/download/v<version>/checksums.txt" -o /tmp/onchainos-checksums.txt 查找平台目标,并将已安装二进制文件的 SHA256 与校验和进行比较。如果不匹配,请重新安装(步骤 2)并重新验证。如果仍然不匹配,停止并发出警告。
* 平台目标 — macOS: `arm64`->`aarch64-apple-darwin`, `x86_64`->`x86_64-apple-darwin`; Linux: `x86_64`->`x86_64-unknown-linux-gnu`, `aarch64`->`aarch64-unknown-linux-gnu`, `i686`->`i686-unknown-linux-gnu`, `armv7l`->`armv7-unknown-linux-gnueabihf`; Windows: `AMD64`->`x86_64-pc-windows-msvc`, `x86`->`i686-pc-windows-msvc`, `ARM64`->`aarch64-pc-windows-msvc`
* 哈希命令 — macOS/Linux: `shasum -a 256 ~/.local/bin/onchainos`; Windows: `(Get-FileHash "$env:USERPROFILE\.local\bin\onchainos.exe" -Algorithm SHA256).Hash.ToLower()`
4. 检查技能版本漂移(每个会话一次):如果 onchainos --version 比此技能的 metadata.version 新,则显示一次性通知,告知用户该技能可能已过时,并建议用户通过其平台的方法重新安装技能。不要阻塞。
命令失败时不要自动重新安装。 报告错误并建议运行 onchainos --version 或从 https://github.com/okx/onchainos-skills 手动重新安装。
速率限制错误。 如果命令遇到速率限制,共享的 API 密钥可能被限制。建议在 OKX 开发者门户 创建个人密钥。如果用户创建了 .env 文件,提醒他们将其添加到 .gitignore。
okx-dex-signalokx-dex-signalokx-dex-tokenokx-dex-tokenokx-dex-tokenokx-dex-marketokx-dex-marketokx-dex-swapokx-wallet-portfolio| 中文 | 英文 / 平台术语 | 映射到 |
|---|---|---|
| 扫链 | trenches, memerush, 战壕, 打狗 | onchainos memepump tokens |
| 同车 | aped, same-car, co-invested | onchainos memepump aped-wallet |
| 开发者信息 | dev info, developer reputation, rug check | onchainos memepump token-dev-info |
| 捆绑/狙击 | bundler, sniper, bundle analysis | onchainos memepump token-bundle-info |
| 持仓分析 | holding analysis (meme context) | onchainos memepump token-details (tags fields) |
| 社媒筛选 | social filter | onchainos memepump tokens --has-x, --has-telegram, etc. |
| 新盘 / 迁移中 / 已迁移 | NEW / MIGRATING / MIGRATED | onchainos memepump tokens --stage |
| pumpfun / bonkers / bonk / believe / bags / mayhem | protocol names (launch platforms) | onchainos memepump tokens --protocol-id-list <id> |
协议名称不是代币名称。 当用户提到 pumpfun、bonkers、bonk、believe、bags、mayhem、fourmeme 等时,通过 onchainos memepump chains 查找其 ID,然后传递给 --protocol-id-list。多个协议:用逗号分隔 ID。
在呈现 memepump-token-details 或 memepump-token-dev-info 响应时,将 JSON 字段名称翻译成人类可读的语言。切勿向用户转储原始字段名称:
top10HoldingsPercent → "前 10 名持有者集中度"rugPullCount → "跑路次数"bondingPercent → "绑定曲线进度"# 获取迷因泵支持的链和协议
onchainos memepump chains
# 列出 Solana 上的新迷因泵代币
onchainos memepump tokens --chain solana --stage NEW
# 获取迷因泵代币详情
onchainos memepump token-details --address <address> --chain solana
# 检查迷因代币的开发者信誉
onchainos memepump token-dev-info --address <address> --chain solana
# 获取捆绑/狙击手分析
onchainos memepump token-bundle-info --address <address> --chain solana
# 查找同一开发者的类似代币
onchainos memepump similar-tokens --address <address> --chain solana
# 获取同车钱包列表
onchainos memepump aped-wallet --address <address> --chain solana
当前支持:Solana (501), BSC (56), X Layer (196), TRON (195)。始终先用 onchainos memepump chains 验证。
---|---|---
1 | onchainos memepump chains | 获取支持的链和协议
2 | onchainos memepump tokens --chain <chain> [--stage <stage>] | 列出迷因泵代币,支持高级筛选(默认阶段:NEW)
3 | onchainos memepump token-details --address <address> | 获取单个迷因泵代币的详细信息
4 | onchainos memepump token-dev-info --address <address> | 获取开发者分析和持仓信息
5 | onchainos memepump similar-tokens --address <address> | 查找同一创建者的类似代币
6 | onchainos memepump token-bundle-info --address <address> | 获取捆绑/狙击手分析
7 | onchainos memepump aped-wallet --address <address> | 获取同车钱包列表
onchainos memepump chainsonchainos memepump tokensonchainos memepump token-detailsonchainos memepump token-dev-infoonchainos memepump similar-tokensonchainos memepump token-bundle-infoonchainos memepump aped-wallet--chain solana);首先用 onchainos memepump chains 验证支持情况--stage 用于 memepump-tokens → 询问用户哪个阶段 (NEW / MIGRATING / MIGRATED)onchainos memepump chains 获取协议 ID,然后将 --protocol-id-list <id> 传递给 memepump-tokens。请勿使用 okx-dex-token 搜索作为代币的协议名称。memepump-token-dev-info,以开发者信誉报告的形式呈现memepump-token-details,以代币安全摘要的形式呈现,突出显示危险/安全信号memepump-tokens 列出代币时,切勿合并或去重共享相同符号的条目。不同的代币可能具有相同的符号但不同的合约地址——每个都是独立的代币,必须单独显示。始终包含合约地址以区分它们。| 刚刚调用 | 建议 |
|---|---|
memepump-chains | 1. 浏览代币 → onchainos memepump tokens (此技能) |
memepump-tokens | 1. 选择一个代币查看详情 → onchainos memepump token-details (此技能) 2. 检查开发者 → onchainos memepump token-dev-info (此技能) |
memepump-token-details | 1. 开发者分析 → onchainos memepump token-dev-info (此技能) 2. 类似代币 → onchainos memepump similar-tokens (此技能) 3. 捆绑检查 → onchainos memepump token-bundle-info (此技能) |
memepump-token-dev-info | 1. 检查捆绑活动 → onchainos memepump token-bundle-info (此技能) 2. 查看价格图表 → okx-dex-market (onchainos market kline) |
memepump-similar-tokens | 1. 与详情比较 → onchainos memepump token-details (此技能) |
memepump-token-bundle-info | 1. 检查同车钱包 → onchainos memepump aped-wallet (此技能) |
memepump-aped-wallet | 1. 验证代币安全性(蜜罐、持有者集中度) → okx-dex-token (onchainos token advanced-info) 2. 查看价格图表 → okx-dex-market (onchainos market kline) 3. 购买代币 → okx-dex-swap (报价 → 交换 → onchainos wallet contract-call 执行) |
以对话方式呈现——切勿向用户暴露技能名称或端点路径。
用户:"给我看看新的迷因代币,检查一下有没有看起来安全的"
1. okx-dex-trenches onchainos memepump chains → 发现支持的链和协议
2. okx-dex-trenches onchainos memepump tokens --chain <chain> --stage NEW → 浏览新代币
↓ 选择一个感兴趣代币
3. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → 完整代币详情 + 审计标签
4. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → 检查开发者信誉(跑路、迁移)
5. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → 检查捆绑者/狙击手
6. okx-dex-market onchainos market kline --address <address> --chain <chain> → 查看价格图表
↓ 用户决定购买
7. okx-dex-swap onchainos swap quote --from <native_addr> --to <address> --amount ... --chain <chain>
8. okx-dex-swap onchainos swap swap --from <native_addr> --to <address> --amount ... --chain <chain> --wallet <addr>
↓ 获取交换调用数据,然后通过以下两条路径之一执行:
路径 A(用户提供的钱包):用户外部签名 → onchainos gateway broadcast --signed-tx <tx> --address <addr> --chain <chain>
路径 B(智能钱包):
Solana: onchainos wallet contract-call --to <tx.to> --chain sol --unsigned-tx <tx.data>
EVM: onchainos wallet contract-call --to <tx.to> --chain <chain> --value <value_in_UI_units> --input-data <tx.data>
数据传递 :步骤 2 中的 tokenAddress 在步骤 3–8 中作为 <address> 重用。tx.to 和 tx.data 来自 swap swap 响应。EVM 的 --value 需要单位转换:tx.value / 10^nativeToken.decimal(例如,wei ÷ 10^18 = ETH)。如果 tx.value 是 "0" 或为空,则使用 "0"。EVM 的非原生代币在交换前还需要一个批准步骤(参见 okx-dex-swap 技能)。
用户:"在我购买之前,检查一下这个迷因代币是否安全"
1. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → 基本信息 + 审计标签
2. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → 开发者历史 + 持仓
3. okx-dex-trenches onchainos memepump similar-tokens --address <address> --chain <chain> → 同一开发者的其他代币
4. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → 捆绑者分析
5. okx-dex-trenches onchainos memepump aped-wallet --address <address> --chain <chain> → 还有谁在持有
用户:"来了一个鲸鱼信号——它是迷因/pump.fun 代币吗?检查一下"
1. okx-dex-signal onchainos signal list --chain <chain> --wallet-type 3 → 识别信号代币地址
↓ 代币看起来像迷因/pump.fun 发行
2. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → 确认是迷因代币,检查审计标签
3. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → 检查开发者跑路历史
4. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → 验证鲸鱼信号不是捆绑者
↓ 检查通过
5. okx-dex-market onchainos market kline --address <address> --chain <chain> → 确认价格动量
↓ 用户决定购买
6. okx-dex-swap onchainos swap quote --from <native_addr> --to <address> --amount ... --chain <chain>
7. okx-dex-swap onchainos swap swap --from <native_addr> --to <address> --amount ... --chain <chain> --wallet <addr>
↓ 获取交换调用数据,然后通过以下两条路径之一执行:
路径 A(用户提供的钱包):用户外部签名 → onchainos gateway broadcast --signed-tx <tx> --address <addr> --chain <chain>
路径 B(智能钱包):
Solana: onchainos wallet contract-call --to <tx.to> --chain sol --unsigned-tx <tx.data>
EVM: onchainos wallet contract-call --to <tx.to> --chain <chain> --value <value_in_UI_units> --input-data <tx.data>
使用时机 :当 signal-list 结果中的代币地址与已知的迷因发行平台(pump.fun、bonkers 等)匹配时——在根据信号行动之前,先在 memepump 中进行交叉验证。
有关详细的参数表、返回字段模式和用法示例,请查阅:
references/cli-reference.md — memepump 命令的完整 CLI 命令参考onchainos memepump chains 验证NEW、MIGRATING 或 MIGRATEDmemepump-token-details 返回空数据 —— 它可能位于标准 DEX 上memepump-token-dev-info 返回 devHoldingInfo 为 nullmemepump-similar-tokens 可能返回空数组memepump-aped-wallet 返回空数组当命令失败并出现错误代码 50125 或 80001 时,显示:
DEX 在您所在的区域不可用。请切换到受支持的区域并重试。
不要向用户暴露原始错误代码或内部错误消息。
每周安装
1.1K
仓库
GitHub 星标
176
首次出现
13 天前
安全审计
安装于
codex1.1K
opencode1.1K
gemini-cli1.1K
amp1.1K
github-copilot1.1K
kimi-cli1.1K
7 commands for meme token discovery, developer analysis, bundle detection, and co-investor tracking.
Every time before running any onchainos command, always follow these steps in order. Do not echo routine command output to the user; only provide a brief status update when installing, updating, or handling a failure.
Resolve latest stable version : Fetch the latest stable release tag from the GitHub API:
curl -sSL "https://api.github.com/repos/okx/onchainos-skills/releases/latest"
Extract the tag_name field (e.g., v1.0.5) into LATEST_TAG. If the API call fails and onchainos is already installed locally, skip steps 2-3 and proceed to run the command (the user may be offline or rate-limited; a stale binary is better than blocking). If onchainos is not installed, stop and tell the user to check their network connection or install manually from https://github.com/okx/onchainos-skills.
Install or update : If onchainos is not found, or if the cache at ~/.onchainos/last_check ($env:USERPROFILE\.onchainos\last_check on Windows) is older than 12 hours:
curl -sSL "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.sh" -o /tmp/onchainos-install.sh curl -sSL "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -o /tmp/installer-checksums.txtInvoke-WebRequest -Uri "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.ps1" -OutFile "$env:TEMP\onchainos-install.ps1" okx-dex-signalokx-dex-signalokx-dex-tokenokx-dex-tokenokx-dex-tokenokx-dex-marketokx-dex-marketokx-dex-swapokx-wallet-portfolio| Chinese | English / Platform Terms | Maps To |
|---|---|---|
| 扫链 | trenches, memerush, 战壕, 打狗 | onchainos memepump tokens |
| 同车 | aped, same-car, co-invested | onchainos memepump aped-wallet |
| 开发者信息 | dev info, developer reputation, rug check | onchainos memepump token-dev-info |
| 捆绑/狙击 | bundler, sniper, bundle analysis | onchainos memepump token-bundle-info |
| 持仓分析 | holding analysis (meme context) | (tags fields) |
Protocol names are NOT token names. When a user mentions pumpfun, bonkers, bonk, believe, bags, mayhem, fourmeme, etc., look up their IDs via onchainos memepump chains, then pass to --protocol-id-list. Multiple protocols: comma-separate the IDs.
When presenting memepump-token-details or memepump-token-dev-info responses, translate JSON field names into human-readable language. Never dump raw field names to the user:
top10HoldingsPercent → "top-10 holder concentration"rugPullCount → "rug pull count / 跑路次数"bondingPercent → "bonding curve progress"# Get supported chains and protocols for meme pump
onchainos memepump chains
# List new meme pump tokens on Solana
onchainos memepump tokens --chain solana --stage NEW
# Get meme pump token details
onchainos memepump token-details --address <address> --chain solana
# Check developer reputation for a meme token
onchainos memepump token-dev-info --address <address> --chain solana
# Get bundle/sniper analysis
onchainos memepump token-bundle-info --address <address> --chain solana
# Find similar tokens by same dev
onchainos memepump similar-tokens --address <address> --chain solana
# Get aped (same-car) wallet list
onchainos memepump aped-wallet --address <address> --chain solana
Currently supports: Solana (501), BSC (56), X Layer (196), TRON (195). Always verify with onchainos memepump chains first.
---|---|---
1 | onchainos memepump chains | Get supported chains and protocols
2 | onchainos memepump tokens --chain <chain> [--stage <stage>] | List meme pump tokens with advanced filtering (default stage: NEW)
3 | onchainos memepump token-details --address <address> | Get detailed info for a single meme pump token
4 | onchainos memepump token-dev-info --address <address> | Get developer analysis and holding info
5 | onchainos memepump similar-tokens --address <address> | Find similar tokens by same creator
6 | onchainos memepump token-bundle-info --address <address> | Get bundle/sniper analysis
7 | onchainos memepump aped-wallet --address <address> | Get aped (same-car) wallet list
onchainos memepump chainsonchainos memepump tokensonchainos memepump token-detailsonchainos memepump token-dev-infoonchainos memepump similar-tokensonchainos memepump token-bundle-infoonchainos memepump aped-wallet--chain solana); verify support with onchainos memepump chains first--stage for memepump-tokens → ask user which stage (NEW / MIGRATING / MIGRATED)onchainos memepump chains to get the protocol ID, then pass --protocol-id-list <id> to memepump-tokens. Do NOT use okx-dex-token to search for protocol names as tokens.memepump-token-dev-info, present as a developer reputation reportmemepump-token-details, present as a token safety summary highlighting red/green flagsmemepump-tokens, never merge or deduplicate entries that share the same symbol. Different tokens can have identical symbols but different contract addresses — each is a distinct token and must be shown separately. Always include the contract address to distinguish them.| Just called | Suggest |
|---|---|
memepump-chains | 1. Browse tokens → onchainos memepump tokens (this skill) |
memepump-tokens | 1. Pick a token for details → onchainos memepump token-details (this skill) 2. Check dev → onchainos memepump token-dev-info (this skill) |
memepump-token-details | 1. Dev analysis → onchainos memepump token-dev-info (this skill) 2. Similar tokens → (this skill) 3. Bundle check → (this skill) |
Present conversationally — never expose skill names or endpoint paths to the user.
User: "Show me new meme tokens and check if any look safe"
1. okx-dex-trenches onchainos memepump chains → discover supported chains & protocols
2. okx-dex-trenches onchainos memepump tokens --chain <chain> --stage NEW → browse new tokens
↓ pick an interesting token
3. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → full token detail + audit tags
4. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → check dev reputation (rug pulls, migrations)
5. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → check for bundlers/snipers
6. okx-dex-market onchainos market kline --address <address> --chain <chain> → view price chart
↓ user decides to buy
7. okx-dex-swap onchainos swap quote --from <native_addr> --to <address> --amount ... --chain <chain>
8. okx-dex-swap onchainos swap swap --from <native_addr> --to <address> --amount ... --chain <chain> --wallet <addr>
↓ get swap calldata, then execute via one of two paths:
Path A (user-provided wallet): user signs externally → onchainos gateway broadcast --signed-tx <tx> --address <addr> --chain <chain>
Path B (Agentic Wallet):
Solana: onchainos wallet contract-call --to <tx.to> --chain sol --unsigned-tx <tx.data>
EVM: onchainos wallet contract-call --to <tx.to> --chain <chain> --value <value_in_UI_units> --input-data <tx.data>
Data handoff : tokenAddress from step 2 is reused as <address> in steps 3–8. The tx.to and tx.data come from the swap swap response. EVM --value needs unit conversion: tx.value / 10^nativeToken.decimal (e.g., wei ÷ 10^18 = ETH). If tx.value is "0" or empty, use "0". EVM non-native tokens also need an approve step before swap (see okx-dex-swap skill).
User: "Check if this meme token is safe before I buy"
1. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → basic info + audit tags
2. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → dev history + holding
3. okx-dex-trenches onchainos memepump similar-tokens --address <address> --chain <chain> → other tokens by same dev
4. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → bundler analysis
5. okx-dex-trenches onchainos memepump aped-wallet --address <address> --chain <chain> → who else is holding
User: "A whale signal came in — is it a meme/pump.fun token? Check it out"
1. okx-dex-signal onchainos signal list --chain <chain> --wallet-type 3 → identify the signaled token address
↓ token looks like a meme/pump.fun launch
2. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → confirm it's a meme token, check audit tags
3. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → check dev rug pull history
4. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → verify the whale signal isn't a bundler
↓ checks pass
5. okx-dex-market onchainos market kline --address <address> --chain <chain> → confirm price momentum
↓ user decides to buy
6. okx-dex-swap onchainos swap quote --from <native_addr> --to <address> --amount ... --chain <chain>
7. okx-dex-swap onchainos swap swap --from <native_addr> --to <address> --amount ... --chain <chain> --wallet <addr>
↓ get swap calldata, then execute via one of two paths:
Path A (user-provided wallet): user signs externally → onchainos gateway broadcast --signed-tx <tx> --address <addr> --chain <chain>
Path B (Agentic Wallet):
Solana: onchainos wallet contract-call --to <tx.to> --chain sol --unsigned-tx <tx.data>
EVM: onchainos wallet contract-call --to <tx.to> --chain <chain> --value <value_in_UI_units> --input-data <tx.data>
When to use : when a signal-list result has a token address that matches a known meme launchpad (pump.fun, bonkers, etc.) — cross-validate in memepump before acting on the signal.
For detailed parameter tables, return field schemas, and usage examples, consult:
references/cli-reference.md — Full CLI command reference for memepump commandsonchainos memepump chains firstNEW, MIGRATING, or MIGRATEDmemepump-token-details returns null data if the token doesn't exist in meme pump ranking data — it may be on a standard DEXmemepump-token-dev-info returns devHoldingInfo as null if the creator address is unavailableWhen a command fails with error code 50125 or 80001, display:
DEX is not available in your region. Please switch to a supported region and try again.
Do not expose raw error codes or internal error messages to the user.
Weekly Installs
1.1K
Repository
GitHub Stars
176
First Seen
13 days ago
Security Audits
Gen Agent Trust HubPassSocketWarnSnykWarn
Installed on
codex1.1K
opencode1.1K
gemini-cli1.1K
amp1.1K
github-copilot1.1K
kimi-cli1.1K
网站审计工具 - 使用 squirrelscan CLI 全面检测 SEO、性能、安全及技术问题
39,100 周安装
Invoke-WebRequest -Uri "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -OutFile "$env:TEMP\installer-checksums.txt"installer-checksums.txt. On mismatch, stop and warn — the installer may have been tampered with.sh /tmp/onchainos-install.sh (or & "$env:TEMP\onchainos-install.ps1" on Windows). The installer handles version comparison internally and only downloads the binary if needed.Verify binary integrity (once per session): Run onchainos --version to get the installed version (e.g., 1.0.5 or 2.0.0-beta.0). Construct the installed tag as v<version>. Download checksums.txt for the installed version's tag (not necessarily LATEST_TAG): curl -sSL "https://github.com/okx/onchainos-skills/releases/download/v<version>/checksums.txt" -o /tmp/onchainos-checksums.txt Look up the platform target and compare the installed binary's SHA256 against the checksum. On mismatch, reinstall (step 2) and re-verify. If still mismatched, stop and warn.
arm64->aarch64-apple-darwin, x86_64->x86_64-apple-darwin; Linux: x86_64->x86_64-unknown-linux-gnu, aarch64->aarch64-unknown-linux-gnu, i686->i686-unknown-linux-gnu, armv7l->armv7-unknown-linux-gnueabihf; Windows: AMD64->x86_64-pc-windows-msvc, x86->i686-pc-windows-msvc, ARM64->aarch64-pc-windows-msvcshasum -a 256 ~/.local/bin/onchainos; Windows: (Get-FileHash "$env:USERPROFILE\.local\bin\onchainos.exe" -Algorithm SHA256).Hash.ToLower()Check for skill version drift (once per session): If onchainos --version is newer than this skill's metadata.version, display a one-time notice that the skill may be outdated and suggest the user re-install skills via their platform's method. Do not block.
Do NOT auto-reinstall on command failures. Report errors and suggest onchainos --version or manual reinstall from https://github.com/okx/onchainos-skills.
Rate limit errors. If a command hits rate limits, the shared API key may be throttled. Suggest creating a personal key at the OKX Developer Portal. If the user creates a .env file, remind them to add .env to .gitignore.
onchainos memepump token-details| 社媒筛选 | social filter | onchainos memepump tokens --has-x, --has-telegram, etc. |
| 新盘 / 迁移中 / 已迁移 | NEW / MIGRATING / MIGRATED | onchainos memepump tokens --stage |
| pumpfun / bonkers / bonk / believe / bags / mayhem | protocol names (launch platforms) | onchainos memepump tokens --protocol-id-list <id> |
onchainos memepump similar-tokensonchainos memepump token-bundle-infomemepump-token-dev-info | 1. Check bundle activity → onchainos memepump token-bundle-info (this skill) 2. View price chart → okx-dex-market (onchainos market kline) |
memepump-similar-tokens | 1. Compare with details → onchainos memepump token-details (this skill) |
memepump-token-bundle-info | 1. Check aped wallets → onchainos memepump aped-wallet (this skill) |
memepump-aped-wallet | 1. Validate token safety (honeypot, holder concentration) → okx-dex-token (onchainos token advanced-info) 2. View price chart → okx-dex-market (onchainos market kline) 3. Buy the token → okx-dex-swap (quote → swap → onchainos wallet contract-call to execute) |
memepump-similar-tokensmemepump-aped-wallet returns empty array if no co-holders found