Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add nirholas/three.ws --skill binance-token-infogit clone --depth 1 https://github.com/nirholas/three.wsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nirholas/three.ws/binance-token-info)<a href="https://agentmods.dev/skills/nirholas/three.ws/binance-token-info"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/binance-token-info/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nirholas/three.ws/binance-token-info"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/binance-token-info.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.03944 |
| Opus 5.5 | $0.00021 | $0.01578 |
| Sonnet 5.5 | $0.00011 | $0.00789 |
| Haiku 4.5 | $0.00005 | $0.00394 |
Grade A, and why
binance-token-info scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --location 'https://web3.binance.com/bapi/defi/v5/public/wallet-direct/buw/wallet/market/token/search?keyword=xxx&chainIds=56,8453,CT_501&orderBy=volume24h' \ This is a copy
88% identical to query-token-info — 50 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Token Info Skill
Overview
| API | Function | Use Case |
|---|---|---|
| Token Search | Search tokens | Find tokens by name, symbol, or contract address |
| Token Metadata | Static info | Get token details,name,symbol,logo, social links, creator address |
| Token Dynamic Data | Real-time market data | Price, volume, holders, liquidity, market cap |
| Token K-Line | Candlestick charts | OHLCV data for technical analysis |
Use Cases
- Search Tokens: Find tokens by name, symbol, or contract address across chains
- Project Research: Get token metadata, social links, and creator info
- Market Analysis: Real-time price, volume, holder distribution, and liquidity data
- Chart Analysis: K-Line candlestick data for technical analysis
Supported Chains
| Chain Name | chainId |
|---|---|
| BSC | 56 |
| Base | 8453 |
| Solana | CT_501 |
API 1: Token Search
Method: GET
URL:
https://web3.binance.com/bapi/defi/v5/public/wallet-direct/buw/wallet/market/token/search
Request Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| keyword | string | Yes | Search keyword (name/symbol/contract address) |
| chainIds | string | No | Chain ID list, comma-separated, e.g., 56,8453,CT_501 |
| orderBy | string | No | Sort field, e.g., volume24h |
Request Headers:
Accept-Encoding: identity
Example Request:
curl --location 'https://web3.binance.com/bapi/defi/v5/public/wallet-direct/buw/wallet/market/token/search?keyword=xxx&chainIds=56,8453,CT_501&orderBy=volume24h' \
--header 'Accept-Encoding: identity'
Response Example:
{
"code": "000000",
"data": [
{
"chainId": "56",
"contractAddress": "0x1234...",
"tokenId": "CC1F457...",
"name": "Token",
"symbol": "symbol of token",
"icon": "/images/web3-data/public/token/logos/xxx.png",
"price": "47.98771375939603199404",
"percentChange24h": "-0.01",
"volume24h": "53687246.955803546359104902201",
"marketCap": "162198400",
"liquidity": "13388877.147327333572157",
"tokenAddresses": [...],
"tagsInfo": {
"AI Analysis": [{"tagName": "AI Widget", "languageKey": "wmp-label-title-ai-widget"}],
"Community Recognition Level": [{"tagName": "Alpha", "languageKey": "wmp-label-title-alpha"}]
},
"links": [
{"label": "website", "link": "https://www.web.site/"},
{"label": "x", "link": "https://twitter.com/..."}
],
"createTime": 1600611727000,
"holdersTop10Percent": "93.267178480644823",
"riskLevel": null
}
],
"success": true
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 441 lines · 53 tokens per session scan A df43c1ed9676
binance-token-info is a skill published in the GitHub repository nirholas/three.ws (250 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 3,944 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 88% identical to query-token-info, differing in 50 lines, and is treated as a copy.
Other skills, from other repositories
evm
Read-only EVM client: wallets, tokens, gas across 8 chains.
hyperliquid
Hyperliquid market data, account history, trade review.
solana
Query Solana wallets, tokens, txs, and NFTs in USD.
mpp-agent
Pay HTTP 402 APIs via Machine Payments Protocol (MPP).
crypto-data
Use for any crypto data question — token/coin prices, FX, commodities, stocks, OHLC history, DEX pairs and liquidity, DeFi TVL, yield/APY pools, or raw JSON-RPC against a chain; also when the user asks for on-chain SQL, wallet labels/net worth, social mindshare or crypto news, so they are told plainly what BlockRun…
polymarket-trading
Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's blockrunmarkets). Covers setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling, and the end-to-end demo flow.