Agent Skills
› ccxt/ccxt
› query-token-audit
query-token-audit
GitHub用于查询代币安全审计,检测诈骗、蜜罐及恶意合约风险。支持在交易前验证代币安全性,识别隐藏风险和异常税率,保障用户资产安全。
Trigger Scenarios
用户询问代币是否安全
检查代币安全性
审计代币
任何交换操作前
Install
npx skills add ccxt/ccxt --skill query-token-audit -g -y
SKILL.md
Frontmatter
{
"name": "query-token-audit",
"metadata": {
"author": "binance-web3-team",
"version": "1.4"
},
"description": "Query token security audit to detect scams, honeypots, and malicious contracts before trading.\nReturns comprehensive security analysis including contract risks, trading risks, and scam detection.\nUse when users ask \"is this token safe?\", \"check token security\", \"audit token\", or before any swap.\n"
}
Query Token Audit Skill
Overview
| API | Function | Use Case |
|---|---|---|
| Token Security Audit | Token security scan | Detect honeypot, rug pull, scam, malicious functions |
Use Cases
- Pre-Trade Safety Check: Verify token security before buying or swapping
- Scam Detection: Identify honeypots, fake tokens, and malicious contracts
- Contract Analysis: Check for dangerous ownership functions and hidden risks
- Tax Verification: Detect unusual buy/sell taxes before trading
Supported Chains
| Chain Name | chainId |
|---|---|
| BSC | 56 |
| Base | 8453 |
| Solana | CT_501 |
| Ethereum | 1 |
API: Token Security Audit
Method: POST
URL:
https://web3.binance.com/bapi/defi/v1/public/wallet-direct/security/token/audit
Request Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| binanceChainId | string | Yes | Chain ID: CT_501 (Solana), 56 (BSC), 8453 (Base), 1 (Ethereum) |
| contractAddress | string | Yes | Token contract address |
| requestId | string | Yes | Unique request ID (UUID v4 format) |
Request Headers:
Content-Type: application/json
Accept-Encoding: identity
User-Agent: binance-web3/1.4 (Skill)
Example Request:
curl --location 'https://web3.binance.com/bapi/defi/v1/public/wallet-direct/security/token/audit' \
--header 'Content-Type: application/json' \
--header 'source: agent' \
--header 'Accept-Encoding: identity' \
--header 'User-Agent: binance-web3/1.4 (Skill)' \
--data '{
"binanceChainId": "56",
"contractAddress": "0x55d398326f99059ff775485246999027b3197955",
"requestId": "'$(uuidgen)'"
}'
Response Example:
{
"code": "000000",
"data": {
"requestId": "d6727c70-de6c-4fad-b1d7-c05422d5f26b",
"hasResult": true,
"isSupported": true,
"riskLevelEnum": "LOW",
"riskLevel": 1,
"extraInfo": {
"buyTax": "0",
"sellTax": "0",
"isVerified": true
},
"riskItems": [
{
"id": "CONTRACT_RISK",
"name": "Contract Risk",
"details": [
{
"title": "Honeypot Risk Not Found",
"description": "A honeypot is a token that can be bought but not sold",
"isHit": false,
"riskType": "RISK"
}
]
}
]
},
"success": true
}
Response Fields:
| Field | Type | Description |
|---|---|---|
| hasResult | boolean | Whether audit data is available |
| isSupported | boolean | Whether the token is supported for audit |
| riskLevelEnum | string | Risk level: LOW, MEDIUM, HIGH |
| riskLevel | number | Risk level number (1-5) |
| extraInfo.buyTax | string | Buy tax percentage (null if unknown) |
| extraInfo.sellTax | string | Sell tax percentage (null if unknown) |
| extraInfo.isVerified | boolean | Whether contract code is verified |
| riskItems[].id | string | Risk category: CONTRACT_RISK, TRADE_RISK, SCAM_RISK |
| riskItems[].details[].title | string | Risk check title |
| riskItems[].details[].description | string | Risk check description |
| riskItems[].details[].isHit | boolean | true = risk detected |
| riskItems[].details[].riskType | string | RISK (critical) or CAUTION (warning) |
Risk Level Reference:
| riskLevel | riskLevelEnum | Action | Description |
|---|---|---|---|
| 0-1 | LOW | Proceed with caution | Lower risk detected, but NOT guaranteed safe. DYOR. |
| 2-3 | MEDIUM | Exercise caution | Moderate risks detected, review risk items carefully |
| 4 | HIGH | Avoid trading | Critical risks detected, high probability of loss |
| 5 | HIGH | Block transaction | Severe risks confirmed, do NOT proceed |
IMPORTANT: LOW risk does NOT mean "safe." Audit results are point-in-time snapshots. Project teams can modify contracts or restrict liquidity after purchase. These risks cannot be predicted in advance.
Response Handling:
- If
hasResult=falseORisSupported=false: → Reply: "Security audit data is not available for this token on this chain." → Do NOT showriskLevel,riskLevelEnum, orriskItems(data is unreliable when either field is false) → You may suggest the user verify the contract address and chain, or try again later - If
hasResult=trueANDisSupported=true: → Show the full audit result including risk level, tax info, and all risk items → Apply the Risk Level Reference table above for actionable guidance
User Agent Header
Include User-Agent header with the following string: binance-web3/1.4 (Skill)
Notes
- All numeric fields are string format, convert when using
- Audit results are ONLY valid when
hasResult: trueANDisSupported: true riskLevel: 5means transaction should be blocked;riskLevel: 4is high risk- Tax thresholds: >10% is critical, 5-10% is warning, <5% is acceptable
- Generate unique UUID v4 for each audit request
- Only output security check risk flags, do NOT provide any investment advice
- Always end with disclaimer:
⚠️ This audit result is for reference only and does not constitute investment advice. Always conduct your own research.
Version History
- 5248956 Current 2026-08-20 07:44


