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 CoinLobster/agent-skills --skill crypto-trade-contextgit clone --depth 1 https://github.com/CoinLobster/agent-skillsWrote 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/coinlobster/agent-skills/crypto-trade-context)<a href="https://agentmods.dev/skills/coinlobster/agent-skills/crypto-trade-context"><img src="https://agentmods.dev/badge/skills/coinlobster/agent-skills/crypto-trade-context/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/coinlobster/agent-skills/crypto-trade-context"><img src="https://agentmods.dev/badge/skills/coinlobster/agent-skills/crypto-trade-context.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.00205 | $0.02116 |
| Opus 5 | $0.00102 | $0.01058 |
| Sonnet 5 | $0.00041 | $0.00423 |
| Haiku 4.5 | $0.00020 | $0.00212 |
Grade B, and why
crypto-trade-context scanned grade B with 2 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 11d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
> curl -s -X POST https://coinlobster.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"market_snapshot","arg Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "The data picture around a crypto position. Use when the user is about to enter or exit, is holding a position and wants what to watch, asks if their side is crowded, what holding costs, whether whales are o How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crypto Trade Context
The user is making or holding a trade. Your job is the data picture, stated so they can decide: crowding as a percentile of the coin's own recorded days, carry cost in dollars, whale direction vs their side, where forced selling actually fired, and what to watch while holding. The decision is theirs; you never make it.
Data sources (in order)
- MCP connected?
coinlobster:trade_context(args:pair, optionalposition_usd, optionalcompact) is the one-call blob: price, 24h stats, funding + OI with percentile judgment vs the pair's own recorded days, whale flow vs the coin's own baseline, visible liquidations, carry arithmetic, crowding (keyed). Keyless it answers on EVERY streamed pair;depthreports which shape you got (liteoff the free pair,free-pair, orkeyed) andlocked_layersnames exactly what a developer plan key (from $29/mo) adds:stats_24h,whale_flow USD magnitudesandcrowding.vs_own_historyis never locked: the percentile judgment is keyless on every pair, here and on/api/public/baselineandmarket_screener. - No MCP: assemble the same picture keyless:
Companion MCP tools when present:curl -s "https://coinlobster.com/api/public/baseline?pair=BTC/USD" # percentile judgment + outcome history curl -s "https://coinlobster.com/api/public/whale-context?coin=BTC" # whale flow vs own baseline (coin param required) curl -s "https://coinlobster.com/api/public/liquidation-history?pair=BTC/USD&limit=100" # history[]: quantity_quote, isBuy (false = a long was force-sold)funding_matrix(per-venue rates, keyless on any streamed pair),squeeze_score(developer plan only: keyless it answersavailable: false),liq_zones(projected levels, labeled as a projection; keyless it covers the free pair only and drops the cascade chains).
On ANY non-200 (401/400/404 alike), fall back and keep a vs-own-history layer in the answer:
/api/public/whale-context?coin=Xcarries the whale multiple, the buy-share baselines AND the USD behind them keyless (ctx.usd24,ctx.net24,ctx.avgDayUsd), which thewhale_contextMCP tool withholds without a key. When the tool locks magnitudes, this endpoint is where you get them. The last 24h of/api/public/crypto-whalesrows embed per-trade funding/OI (marketConditions) for a crude funding-range check. Without an MCP client, every tool answers a raw POST:curl -s -X POST https://coinlobster.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"market_snapshot","arguments":{"pair":"BTC/USD"}}}'
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.
- 11d ago First seen · 67 lines · 205 tokens per session scan B c847987979cb
crypto-trade-context is a skill published in the GitHub repository CoinLobster/agent-skills (9 stars, last pushed 28d ago), licensed MIT. It adds 205 tokens to every session and 2,116 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
crypto-token-analysis
Deep-dive framework for analyzing crypto tokens — market data, liquidity health, tokenomics, unlock schedules, and risk assessment. Combines on-chain data, API queries, and multi-source validation to generate actionable investment verdicts.
crypto-defi-trading
Crypto and DeFi trading: DEX analysis (Uniswap, SushiSwap, Curve), on-chain analytics, MEV detection, impermanent loss, yield farming metrics, DeFi risk analysis, token metrics, liquidity pool analysis, whale tracking, exchange netflow. USE FOR: crypto, defi, dex, uniswap, sushiswap, curve, impermanent loss, yield…
freqtrade-bot
Freqtrade — open-source Python crypto trading bot. Backtesting, hyperopt (ML parameter optimization), FreqAI (self-training adaptive strategies), Telegram + WebUI control. Supports Binance, Kraken, Bybit, OKX, Gate.io (spot + futures). SQLite trade h.
trading-signals
Fetches live AI crypto trading signals with entry price, stop-loss, take-profit, leverage, confidence scores, and automated verification. Covers 50+ coins including BTC, ETH, SOL. Use when the user asks for crypto signals, trade ideas, market direction, portfolio analysis, or wants to build a trading bot.
crypto-derivatives
Crypto-derivatives strategies — perpetual funding-rate arbitrage, futures term-structure contango/backwardation trading, and option volatility-smile / Greeks analysis.
defi-yield
DeFi yield analysis and optimization — lending rates, LP yields, staking returns, yield farming strategies, risk-adjusted yield comparison, and protocol-level sustainability assessment.