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 hive-intel/hive-sdk --skill hive-dex-pool-analysisgit clone --depth 1 https://github.com/hive-intel/hive-sdkWrote 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/hive-intel/hive-sdk/hive-dex-pool-analysis)<a href="https://agentmods.dev/skills/hive-intel/hive-sdk/hive-dex-pool-analysis"><img src="https://agentmods.dev/badge/skills/hive-intel/hive-sdk/hive-dex-pool-analysis.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.01288 |
| Opus 5 | $0.00052 | $0.00644 |
| Sonnet 5 | $0.00021 | $0.00258 |
| Haiku 4.5 | $0.00010 | $0.00129 |
Grade A, and why
hive-dex-pool-analysis scanned grade A with 0 findings 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hive-dex-pool-analysis — DEX And Pool Analysis
Analyze on-chain DEX pools and pairs: liquidity, swaps, OHLCV, trends, and token-level DEX flow, keeping pool-level and token-level facts clearly separate.
Task toolset and identifiers
Toolset: onchain_dex_pool_analysis. Read
hive://toolsets/onchain_dex_pool_analysis before execution; it is
authoritative for the current output schema, material-call budget, phases,
fallback condition, and stop conditions.
- Required: chain/network plus pair/pool address, token contract, or both token sides.
- Optional: DEX name, time window, candle interval, trade direction.
If the user gives only one token, search candidate pools and prefer the pool most relevant by liquidity/volume — and say which pool you chose, because the same pair can have several pools with different fee tiers.
Before choosing endpoints, select exactly one matching entry from the exact workflow's routes[]. Follow its ordered steps, use a fallback only under that step's published condition, stop at four material calls, and preserve the selected route_id in the typed result. The broad coverageCatalog is discovery coverage, not an execution plan.
Procedure
- Resolve chain and pool/pair/token identifiers.
- Call
search_toolsfor pair search, pool info, liquidity, trades, OHLCV, and trending-pool capabilities. - Call
get_api_endpoint_schemafor each endpoint before calling it. - Start with pool/pair metadata and liquidity; add trades/OHLCV for flow or trend questions.
- Report liquidity depth, recent flow, and data freshness.
Bounded calls
- Limit trade lists and candle counts.
- Do not infer token-wide liquidity from one pool without saying so.
- Keep pool-level and token-level metrics separate.
Worked example
User: "How deep is the main PEPE/WETH pool on Ethereum, and which way has flow gone today?"
search_tools→{"query": "dex pair search pool liquidity trades ethereum", "limit": 5}- Resolve candidate pools for PEPE (0x6982508145454Ce325dDbE47a25d4ec3d2311933), pick the deepest PEPE/WETH pool, and state the choice.
get_api_endpoint_schematheninvoke_api_endpointfor pool info, liquidity, and a bounded trade list (explicit limit, today's window).- Report depth, net flow direction, and freshness with the template below.
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.
- 8d ago First seen · 132 lines · 104 tokens per session scan A 837324a3de45
hive-dex-pool-analysis is a skill published in the GitHub repository hive-intel/hive-sdk (18 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 1,288 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
palisade-security-scanner
Onchain security scanner on Robinhood Chain — scan token approvals, detect honeypots, analyze contracts for rugpull indicators, check liquidity locks, and score contract safety. Use when a user asks an agent to evaluate, scan, or check a token or wallet before trading, swapping, signing an approval, or investing. 18…
pump-swarm
Coordinated multi-wallet trading on Pump.fun.
trading-solana
Trade tokens on Solana DEXes - Jupiter, Raydium, Orca, Meteora, Pump.fun.
public
For agents: This document explains how to integrate with Clodds APIs.
copy-trading
Automatically copy trades from successful wallets on Polymarket and crypto.
trading-evm
Trade tokens on EVM chains - Uniswap V3, 1inch on Ethereum, Arbitrum, Optimism, Base, Polygon.