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 rules/jkorf/cryptoexchange.net/cryptoexchange-netgit clone --depth 1 https://github.com/JKorf/CryptoExchange.NetWrote 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/rules/jkorf/cryptoexchange.net/cryptoexchange-net)<a href="https://agentmods.dev/rules/jkorf/cryptoexchange.net/cryptoexchange-net"><img src="https://agentmods.dev/badge/rules/jkorf/cryptoexchange.net/cryptoexchange-net.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.1 | $0.00000 | $0.01059 |
| Opus 5 | $0.00000 | $0.00530 |
| Sonnet 5 | $0.00000 | $0.00212 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
cryptoexchange-net 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 7d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CryptoExchange.Net Conventions
This codebase uses CryptoExchange.Net abstractions for multi-exchange access. Each exchange has its own library (Binance.Net, Bybit.Net, OKX.Net, ...). Use CryptoExchange.Net.SharedApis for code that should work across exchanges.
Multi-exchange pattern
using Binance.Net.Clients;
using OKX.Net.Clients;
using CryptoExchange.Net.SharedApis;
ISpotTickerRestClient binance = new BinanceRestClient().SpotApi.SharedClient;
ISpotTickerRestClient okx = new OKXRestClient().UnifiedApi.SharedClient;
var symbol = new SharedSymbol(TradingMode.Spot, "BTC", "USDT");
var ticker = await binance.GetSpotTickerAsync(new GetTickerRequest(symbol));
// ticker.Data.LastPrice — same model regardless of exchange
Symbol normalization
SharedSymbol(TradingMode.Spot, "BTC", "USDT") is portable. Each library translates to its native format internally. Don't pass raw strings like "BTCUSDT" to shared methods.
Symbol metadata and catalogs
In 12.2.0, SharedSpotSymbol and SharedFuturesSymbol include DisplayName and base/quote asset classification through SharedAssetType (Crypto, Fiat, TradFi) and SharedAssetSubType (StableCoin, Equity, Commodity). Pass the matching base/quote filters to GetSymbolsRequest when discovery should return only a class of markets.
After calling GetSpotSymbolsAsync, ISpotSymbolRestClient.SpotSymbolCatalog maps asset and symbol names to shared metadata. IFuturesSymbolRestClient.FuturesSymbolCatalog works the same way after GetFuturesSymbolsAsync. Treat either property as unavailable before its corresponding request has populated the cache.
When implementing an exchange library, use LibraryHelpers.IsStableCoin, IsCommodity, and IsEquity only as best-effort classifiers and supply exchange-specific additions where needed.
Shared market-data quantities
In 12.4.0, use SharedOrderQuantity-valued Volumes on shared spot/futures tickers and klines, and Quantities on shared trades. The scalar Volume, QuoteVolume, and Quantity members are obsolete.
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.
- 7d ago First seen · 88 lines · 0 tokens per session scan A 92109a661ff2
cryptoexchange-net is a cursor rule published in the GitHub repository JKorf/CryptoExchange.Net (569 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,059 tokens. 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 cursor rules, from other repositories
elizaos_v2_onchain_plugins
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Wallet Provider│ │ Connection Mgmt │ │ Transaction Svc │ │ - Private Keys │───▶│ - RPC Endpoints │───▶│ - Tx Construction│ │ - Public Keys │ │ - Network Config │ │ - Fee Estimation│ │ - Signatures │ │ - Health Check │ │ - Broadcasting │ └─────────────────┘…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.