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 agentmods add skills/nansen-ai/nansen-cli/nansen-limit-ordersnpx skills add nansen-ai/nansen-cli --skill nansen-limit-ordersgit clone --depth 1 https://github.com/nansen-ai/nansen-cliWrote 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/nansen-ai/nansen-cli/nansen-limit-orders)<a href="https://agentmods.dev/skills/nansen-ai/nansen-cli/nansen-limit-orders"><img src="https://agentmods.dev/badge/skills/nansen-ai/nansen-cli/nansen-limit-orders.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.02352 |
| Opus 5 | $0.00028 | $0.01176 |
| Sonnet 5 | $0.00011 | $0.00470 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade A, and why
nansen-limit-orders 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 5d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Limit Orders
Use this skill when the user wants a price-triggered order. There are two distinct paths — pick the one that matches the user's chain:
- Solana → native limit orders.
nansen trade limit-order create|list|cancel|updateplaces real resting orders through the Nansen trading API. Use these for anything on Solana. - Other chains → alert-based approximation.
nansen-clidoes not yet place native limit orders on EVM chains. Place the resting order on the venue that supports it (CEX, DEX limit-order product) and create a companioncommon-token-transfersmart alert on the settlement wallet as a best-effort fill signal.
Prerequisites
- A Solana wallet configured in
nansen-cli:nansen wallet show <name>(ornansen wallet createif none exists). Local, Privy, and WalletConnect wallets are all supported fortrade limit-order. - The wallet must hold the sell token plus a small amount of SOL for fees.
- For the alert fallback: a notification channel (Telegram chat ID, Slack or Discord webhook, or generic webhook URL).
NANSEN_API_KEY. Smart alerts are internal-only; non-internal users get 404.- First-time
trade limit-order createauto-registers a trading vault and caches a JWT at~/.nansen/limit-order-auth.jsonfor ~23h.
Two mechanisms, not one. The limit order itself is price-triggered — it executes when the market price crosses the target. A companion smart alert is a settlement confirmation — it fires after the trade settles on-chain (i.e. when the bought token actually arrives in the wallet). They are independent: the order handles the trigger, the alert tells the user the fill landed.
Solana: Native Limit Orders
Create
# --amount is always in token units (e.g. 1 = 1 SOL, 80 = 80 USDC)
nansen trade limit-order create \
--from SOL --to USDC \
--amount 1 \
--trigger-mint SOL --trigger-condition below --trigger-price 80
# with explicit slippage and expiry
nansen trade limit-order create \
--from SOL --to USDC \
--amount 1.5 \
--trigger-mint SOL --trigger-condition above --trigger-price 200 \
--slippage-bps 300 \
--expires 7d
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.
- 5d ago First seen · 237 lines · 56 tokens per session scan A bafc068cfa0c
nansen-limit-orders is a skill published in the GitHub repository nansen-ai/nansen-cli (134 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 2,352 once invoked, about $0.0003 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
mpp-agent
Pay HTTP 402 APIs via Machine Payments Protocol (MPP).
crypto-market-rank
Crypto market rankings and leaderboards. Query trending tokens, top searched tokens, Binance Alpha tokens, tokenized stocks, social hype sentiment ranks, smart money inflow token rankings, top meme token rankings from Pulse launchpad, and top trader PnL leaderboards. Use this skill when users ask about token rankings…
trading-signal
Subscribe and retrieve on-chain Smart Money signals. Monitor trading activities of smart money addresses, including buy/sell signals, trigger price, current price, max gain, and exit rate. Use this skill when users are looking for investment opportunities — smart money signals can serve as valuable references for…
cobie-cycle-filter
Use when evaluating crypto decisions through a Cobie-style cycle filter: common-sense risk, narrative traps, leverage humility, and avoiding obvious stupid trades.
bridge
Cross-chain token transfers using Wormhole and CCTP.
hyperliquid
Hyperliquid L1 perps DEX (69% market share).