Index of every page on this site: llms.txt
All skills
binance avatar

/query-token-audit

@7d1b1f7
by binancebinance/binance-skills-hub1.2k stars
281
Run it yourself

Query token security audit to detect scams, honeypots, and malicious contracts before trading. Returns comprehensive security analysis including contract risks, trading risks, and scam detection. Use when users ask "is this token safe?", "check token security", "audit token", or before any swap.

Use this Skill: https://skilld.dev/gh/binance/binance-skills-hub/query-token-audit

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈79 tokens for metadata: the name and description. ≈1.5k when used: this file.

Description uses 4.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈316 characters, or 4.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Query Token Audit Skill

Overview

API Function Use Case
Token Security Audit Token security scan Detect honeypot, rug pull, scam, malicious functions

Use Cases

  1. Pre-Trade Safety Check: Verify token security before buying or swapping
  2. Scam Detection: Identify honeypots, fake tokens, and malicious contracts
  3. Contract Analysis: Check for dangerous ownership functions and hidden risks
  4. 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=false OR isSupported=false: → Reply: "Security audit data is not available for this token on this chain." → Do NOT show riskLevel, riskLevelEnum, or riskItems (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=true AND isSupported=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

  1. All numeric fields are string format, convert when using
  2. Audit results are ONLY valid when hasResult: true AND isSupported: true
  3. riskLevel: 5 means transaction should be blocked; riskLevel: 4 is high risk
  4. Tax thresholds: >10% is critical, 5-10% is warning, <5% is acceptable
  5. Generate unique UUID v4 for each audit request
  6. Only output security check risk flags, do NOT provide any investment advice
  7. Always end with disclaimer: ⚠️ This audit result is for reference only and does not constitute investment advice. Always conduct your own research.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill performs security audits on blockchain tokens using the official Binance API. It is safe for its intended purpose but has a surface for indirect prompt injection from malicious token data or API responses.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 7d1b1f7. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 8 months ago
metadata
{
  "author": "binance-web3-team",
  "version": "1.4"
}
  • token-security
  • binance
  • web3
  • honeypot-detection
  • scam-detection
  • contract-audit
  • blockchain
  • solana
  • bsc
  • ethereum

README badge

README badge for binance/binance-skills-hub/query-token-audit

Queries Binance's token security audit API to detect honeypots, rug pulls, and malicious contracts across BSC, Base, Solana, and Ethereum before a user trades. Returns risk levels, buy/sell taxes, and specific contract and trading risks.

Generated from the current SKILL.md.

What chains does this token audit support?
The skill supports BSC (chainId 56), Base (8453), Solana (CT_501), and Ethereum (1).
What risks does the audit detect?
The audit detects honeypots, rug pulls, scams, malicious functions, unusual buy/sell taxes, and dangerous ownership functions. Results are categorized as CONTRACT_RISK, TRADE_RISK, or SCAM_RISK.
Does a LOW risk rating mean the token is safe to trade?
No. LOW risk does not guarantee safety — it is a point-in-time snapshot. Project teams can modify contracts or restrict liquidity after purchase, which the audit cannot predict.
When should I not trust the audit results?
Do not use the results if hasResult=false or isSupported=false. In those cases, audit data is unavailable or unreliable for that token on that chain.

Generated from the current SKILL.md. These answers refresh after source changes.