xt-net

Coding rules for using XT.Net, a C#/.NET library that connects to the XT cryptocurrency exchange.

In plain words
What is it for?
They are for setting up REST and WebSocket clients, reading spot and futures data, handling results, and generating XT API code in .NET projects.
Why use it?
They keep exchange code consistent and avoid common integration mistakes, such as using the wrong client path or reading data before checking for an error.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/jkorf/xt.net/xt-net
Clone the repo
git clone --depth 1 https://github.com/JKorf/XT.Net

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 717 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00717
Opus 5 $0.00000 $0.00358
Sonnet 5 $0.00000 $0.00143
Haiku 4.5 $0.00000 $0.00072

Measured 2d ago against content hash 84f91f85bb08, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

xt-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 2d 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/xt-net.mdc · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

XT.Net Conventions

This codebase uses XT.Net for XT cryptocurrency exchange access. Do not write raw HttpClient calls to XT endpoints.

Client Setup Pattern

using XT.Net;
using XT.Net.Clients;

var restClient = new XTRestClient(options =>
{
    options.ApiCredentials = new XTCredentials("API_KEY", "API_SECRET");
});

For public market data only, no credentials are needed: new XTRestClient().

Result Pattern

All methods return WebCallResult<T> or WebCallResult for REST and CallResult<T> for WebSocket. Always check .Success before reading .Data.

var ticker = await restClient.SpotApi.ExchangeData.GetTickersAsync("eth_usdt");
if (!ticker.Success) { Console.WriteLine(ticker.Error); return; }
var first = ticker.Data.First();

API Surface

  • restClient.SpotApi.{ExchangeData|Account|Trading}
  • restClient.UsdtFuturesApi.{ExchangeData|Account|Trading}
  • restClient.CoinFuturesApi.{ExchangeData|Account|Trading}
  • socketClient.SpotApi
  • socketClient.FuturesApi

Do not generate socketClient.UsdtFuturesApi or socketClient.CoinFuturesApi; futures sockets are under FuturesApi.

WebSocket Pattern

var socketClient = new XTSocketClient();
var sub = await socketClient.SpotApi.SubscribeToTickerUpdatesAsync(
    "eth_usdt",
    update => Console.WriteLine(update.Data.LastPrice));
if (!sub.Success) { Console.WriteLine(sub.Error); return; }

await socketClient.UnsubscribeAsync(sub.Data);

Private spot streams need restClient.SpotApi.Account.GetWebsocketTokenAsync(). Private futures streams need restClient.UsdtFuturesApi.Account.GetListenKeyAsync().

Multi-Exchange Code

For exchange-agnostic code, use CryptoExchange.Net.SharedApis:

using CryptoExchange.Net.SharedApis;

var shared = new XTRestClient().SpotApi.SharedClient;
var ticker = await shared.GetSpotTickerAsync(
    new GetTickerRequest(new SharedSymbol(TradingMode.Spot, "BTC", "USDT")));

Hard Rules

  • Never write raw HttpClient XT endpoint calls.
  • Never use .Result or .Wait(); use await.
  • Never instantiate clients per request; reuse or use DI.
  • Never skip checking WebCallResult.Success.
  • Always use XTCredentials("key", "secret"), not generic ApiCredentials.
  • Always store WebSocket subscriptions and unsubscribe on shutdown.
  • Always inspect XT.Net/Interfaces/Clients/** before generating methods not in the map.

Read the full file on GitHub · 89 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. 2d ago First seen · 89 lines · 0 tokens per session scan A 84f91f85bb08

Subscribe to this mod's changes

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