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/binance.net/binance-netgit clone --depth 1 https://github.com/JKorf/Binance.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/binance.net/binance-net)<a href="https://agentmods.dev/rules/jkorf/binance.net/binance-net"><img src="https://agentmods.dev/badge/rules/jkorf/binance.net/binance-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 | $0.00000 | $0.00927 |
| Opus 5 | $0.00000 | $0.00464 |
| Sonnet 5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
binance-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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Binance.Net Conventions
This codebase uses Binance.Net for Binance cryptocurrency exchange access. Do not write raw HttpClient calls to Binance endpoints.
Client setup pattern
using Binance.Net.Clients;
using Binance.Net;
using Binance.Net.Objects;
var restClient = new BinanceRestClient(options =>
{
options.ApiCredentials = new BinanceCredentials("API_KEY", "API_SECRET");
});
For public market data only, no credentials needed: new BinanceRestClient().
Result pattern
REST methods return HttpResult<T> / HttpResult; WebSocket subscriptions and socket API requests return WebSocketResult<T> / WebSocketResult. Always check .Success before reading .Data:
var ticker = await restClient.SpotApi.ExchangeData.GetTickerAsync("BTCUSDT");
if (!ticker.Success) { /* ticker.Error */ return; }
var price = ticker.Data.LastPrice;
API surface
restClient.SpotApi.{ExchangeData|Account|Trading}restClient.UsdFuturesApi.{ExchangeData|Account|Trading}restClient.CoinFuturesApi.{ExchangeData|Account|Trading}restClient.GeneralApi.{Brokerage|Futures|CryptoLoans|AutoInvest|Mining|SubAccount|Staking|SimpleEarn|CopyTrading|GiftCard|Nft}socketClient.SpotApi.{ExchangeData|Account|Trading}for WebSocket subscriptions and requestssocketClient.UsdFuturesApi.{ExchangeData|Account|Trading}for WebSocket subscriptions and requestssocketClient.CoinFuturesApi.{ExchangeData|Account|Trading}for WebSocket subscriptions
Order placement
Let the library auto-generate clientOrderId. Do not pass a custom one unless required for an existing operational flow:
var order = await restClient.SpotApi.Trading.PlaceOrderAsync(
"BTCUSDT", OrderSide.Buy, SpotOrderType.Limit,
quantity: 0.001m, price: 50000m, timeInForce: TimeInForce.GoodTillCanceled);
WebSocket pattern
var socketClient = new BinanceSocketClient();
var sub = await socketClient.SpotApi.ExchangeData.SubscribeToTickerUpdatesAsync(
"BTCUSDT",
update => { /* update.Data.LastPrice */ });
if (!sub.Success) { /* sub.Error */ return; }
// On shutdown:
await socketClient.UnsubscribeAsync(sub.Data);
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.
- 4d ago First seen · 104 lines · 0 tokens per session scan A 6367175fc654
binance-net is a cursor rule published in the GitHub repository JKorf/Binance.Net (1,172 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 927 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
kucoin-net
Conventions for using Kucoin.Net library when working with Kucoin cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with Kucoin API.
cursorrules
AGENTS.md.
mexc-net
Conventions for using Mexc.Net library when working with the MEXC cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the MEXC API.
hyperliquid-net
Conventions for using HyperLiquid.Net when working with the HyperLiquid DEX in C#/.NET, including spot, futures, account, HIP-3 DEX, and HIP-4 outcome APIs. Apply when generating code that interacts with the HyperLiquid API.
whitebit-net
Conventions for using WhiteBit.Net when working with the WhiteBit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with WhiteBit APIs.
development-workflow
This project uses pnpm for package management and has a structured set of scripts for different development tasks.