crypto-clients-net

crypto-clients-net is a cursor rule for Cursor from JKorf/CryptoClients.Net. It costs 0 tokens per session (691 once invoked), scanned A, original, MIT.

Coding conventions for using CryptoClients.Net in C#/.NET applications that connect to multiple cryptocurrency exchanges.

In plain words
What is it for?
Use them when generating or reviewing aggregate exchange, WebSocket, order-book, tracker, or dynamic-credential code.
Why use it?
They standardise client setup, dependency injection, result checking, and shared exchange API calls, reducing integration mistakes.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions AGENTS.md.

Good fit Use them when generating or reviewing aggregate exchange, WebSocket, order-book, tracker, or dynamic-credential code.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/jkorf/cryptoclients.net/crypto-clients-net
Install

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.

Clone the repo
git clone --depth 1 https://github.com/JKorf/CryptoClients.Net

Made for: Cursor.

Wrote 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.

agentmods badge for crypto-clients-net

README.md
[![agentmods](https://agentmods.dev/badge/rules/jkorf/cryptoclients.net/crypto-clients-net.svg)](https://agentmods.dev/rules/jkorf/cryptoclients.net/crypto-clients-net)
Your own site
<a href="https://agentmods.dev/rules/jkorf/cryptoclients.net/crypto-clients-net"><img src="https://agentmods.dev/badge/rules/jkorf/cryptoclients.net/crypto-clients-net.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 691 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00691
Opus 5 $0.00000 $0.00345
Sonnet 5 $0.00000 $0.00138
Haiku 4.5 $0.00000 $0.00069

Measured 8d ago against content hash 8d2b0db89d0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

crypto-clients-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 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.

.cursor/rules/crypto-clients-net.mdc · 67 lines

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.

CryptoClients.Net Conventions

This codebase uses CryptoClients.Net for multi-exchange cryptocurrency API access. Do not write raw HttpClient calls to exchange endpoints.

Client setup pattern

using CryptoClients.Net;
using CryptoExchange.Net.SharedApis;

var restClient = new ExchangeRestClient();
var socketClient = new ExchangeSocketClient();

For application code, prefer DI:

services.AddCryptoClients(options => options.OutputOriginalData = true);

Result pattern

Aggregate methods return ExchangeWebResult<T>, ExchangeWebResult<T>[], ExchangeResult<UpdateSubscription>, or ExchangeResult<UpdateSubscription>[]. Always check .Success before reading .Data.

var ticker = await restClient.GetSpotTickerAsync(
    "Binance",
    new GetTickerRequest(new SharedSymbol(TradingMode.Spot, "BTC", SharedSymbol.UsdOrStable)));

if (!ticker.Success) { /* ticker.Error */ return; }
var price = ticker.Data.LastPrice;

API surface

  • Aggregate REST: restClient.GetSpotTickerAsync(...), GetFuturesTickerAsync(...), GetOrderBookAsync(...), PlaceSpotOrderAsync(...), etc.
  • Shared REST clients: restClient.GetSpotTickerClient(exchange), GetBalancesClient(...), GetFuturesOrderClient(...), etc.
  • Direct exchange REST: restClient.Binance, restClient.Bybit, restClient.OKX, etc.
  • Aggregate sockets: socketClient.SubscribeToTickerUpdatesAsync(...), SubscribeToOrderBookUpdatesAsync(...), SubscribeToBalanceUpdatesAsync(...), etc.
  • Shared socket clients: socketClient.GetTickerClient(...), GetOrderBookClient(...), GetSpotOrderClient(...), etc.
  • Direct exchange sockets: socketClient.Binance, socketClient.Kucoin, socketClient.OKX, etc.

Hard rules

  • Never skip checking Success.
  • Use SharedSymbol for aggregate/shared APIs. For cross-exchange USD/stable quote routing, prefer SharedSymbol.UsdOrStable instead of hardcoding USDT when USDC/USD variants are acceptable.
  • Handle per-exchange failures independently in multi-exchange results.
  • Use Get*Client(...) null checks when routing manually.
  • Use ExchangeCredentials or DynamicCredentials; do not guess credential shapes.
  • Call subscription.Data.CloseAsync() for one aggregate WebSocket subscription, direct exchange UnsubscribeAsync(subscription.Data) for direct socket clients, or UnsubscribeAllAsync() for all aggregate subscriptions.
  • Use direct exchange properties for full exchange-specific APIs.

Read the full file on GitHub · 67 lines

Changes

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.

  1. 8d ago First seen · 67 lines · 0 tokens per session scan A 8d2b0db89d0f

Subscribe to this mod's changes

crypto-clients-net is a cursor rule published in the GitHub repository JKorf/CryptoClients.Net (45 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 691 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.