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.
git clone --depth 1 https://github.com/JKorf/CoinEx.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/coinex.net/coinex-net)<a href="https://agentmods.dev/rules/jkorf/coinex.net/coinex-net"><img src="https://agentmods.dev/badge/rules/jkorf/coinex.net/coinex-net/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/rules/jkorf/coinex.net/coinex-net"><img src="https://agentmods.dev/badge/rules/jkorf/coinex.net/coinex-net.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.00000 | $0.00953 |
| Opus 5 | $0.00000 | $0.00477 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
coinex-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 10d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoinEx.Net Conventions
This codebase uses CoinEx.Net for CoinEx cryptocurrency exchange access. Do not write raw HttpClient calls to CoinEx endpoints.
Client setup pattern
using CoinEx.Net;
using CoinEx.Net.Clients;
var restClient = new CoinExRestClient(options =>
{
options.ApiCredentials = new CoinExCredentials("API_KEY", "API_SECRET");
});
For public market data only, no credentials are needed: new CoinExRestClient().
Result pattern
All methods return WebCallResult<T> for REST or CallResult<T> for WebSocket. Always check .Success before reading .Data:
var tickers = await restClient.SpotApiV2.ExchangeData.GetTickersAsync(new[] { "BTCUSDT" });
if (!tickers.Success) { /* tickers.Error */ return; }
var price = tickers.Data.First().LastPrice;
API surface
restClient.SpotApiV2.{ExchangeData|Account|Trading}restClient.FuturesApi.{ExchangeData|Account|Trading}socketClient.SpotApiV2for spot WebSocket subscriptionssocketClient.FuturesApifor futures WebSocket subscriptionsrestClient.SpotApiV2.SharedClientandrestClient.FuturesApi.SharedClientsocketClient.SpotApiV2.SharedClientandsocketClient.FuturesApi.SharedClient
Order placement
Spot order placement includes AccountType:
var order = await restClient.SpotApiV2.Trading.PlaceOrderAsync(
"BTCUSDT", AccountType.Spot, OrderSide.Buy, OrderTypeV2.Limit,
quantity: 0.001m, price: 50000m);
Futures order placement does not include AccountType:
var order = await restClient.FuturesApi.Trading.PlaceOrderAsync(
"ETHUSDT", OrderSide.Buy, OrderTypeV2.Market, quantity: 0.01m);
WebSocket pattern
var socketClient = new CoinExSocketClient();
var sub = await socketClient.SpotApiV2.SubscribeToTickerUpdatesAsync(
new[] { "BTCUSDT" },
update => { /* update.Data.First().LastPrice */ });
if (!sub.Success) { /* sub.Error */ return; }
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.
- 10d ago First seen · 107 lines · 0 tokens per session scan A 98aba85b1834
coinex-net is a cursor rule published in the GitHub repository JKorf/CoinEx.Net (55 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 953 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
kraken-net
Conventions for using Kraken.Net when working with Kraken Spot and Futures cryptocurrency exchange APIs in C#/.NET. Apply when generating code that interacts with Kraken API.
binance-net
Conventions for using Binance.Net library when working with Binance cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with Binance API.
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.
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.
bingx-net
Conventions for using BingX.Net library when working with the BingX exchange in C#/.NET. Apply when generating code that interacts with the BingX API.
toobit-net
Conventions for using Toobit.Net when working with the Toobit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the Toobit API.