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/Kraken.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/kraken.net/kraken-net)<a href="https://agentmods.dev/rules/jkorf/kraken.net/kraken-net"><img src="https://agentmods.dev/badge/rules/jkorf/kraken.net/kraken-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/kraken.net/kraken-net"><img src="https://agentmods.dev/badge/rules/jkorf/kraken.net/kraken-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.00788 |
| Opus 5 | $0.00000 | $0.00394 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
kraken-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 9d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kraken.Net Conventions
This codebase uses Kraken.Net for Kraken Spot and Futures exchange access. Do not write raw HttpClient calls to Kraken endpoints.
Client setup pattern
using CryptoExchange.Net.Authentication;
using Kraken.Net;
using Kraken.Net.Clients;
var restClient = new KrakenRestClient(options =>
{
options.ApiCredentials = new KrakenCredentials(
new HMACCredential("SPOT_KEY", "SPOT_SECRET"),
new HMACCredential("FUTURES_KEY", "FUTURES_SECRET"));
});
For public market data only, no credentials are needed: new KrakenRestClient().
Result pattern
All methods return WebCallResult<T> or CallResult<T>. Always check .Success before reading .Data:
var ticker = await restClient.SpotApi.ExchangeData.GetTickerAsync("ETHUSDT");
if (!ticker.Success) { Console.WriteLine(ticker.Error); return; }
var price = ticker.Data.Values.First().LastTrade.Price;
API surface
restClient.SpotApi.{ExchangeData|Account|Trading|Earn}restClient.FuturesApi.{ExchangeData|Account|Trading}socketClient.SpotApifor Spot WebSocket v2 subscriptions and socket order requestssocketClient.FuturesApifor Futures WebSocket subscriptions.SharedClienton Spot/Futures REST and socket APIs forCryptoExchange.Net.SharedApis- Spot socket
.SharedClientimplementsISpotOrderManagementSocketClientfor shared place/cancel order requests - Shared Spot/Futures symbol clients expose symbol catalogs and typed asset metadata; Spot shared symbol discovery includes tokenized assets
Kraken-specific details
- Spot REST symbol examples use
ETHUSDT; Spot WebSocket v2 uses names such asETH/USDT. - Futures symbols use names such as
PF_ETHUSD. - Credentials can differ for Spot and Futures. Prefer
new KrakenCredentials(new HMACCredential(...), new HMACCredential(...)). KrakenEnvironment.Liveis the built-in environment. UseKrakenEnvironment.CreateCustom(...)for custom addresses.- Spot private endpoints can use
twoFactorPassword;KrakenRestOptions.StaticTwoFactorAuthenticationPasswordcan provide a static OTP value for private REST requests.
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.
- 9d ago First seen · 87 lines · 0 tokens per session scan A 225aa0534a68
kraken-net is a cursor rule published in the GitHub repository JKorf/Kraken.Net (118 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 788 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
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.
coinex-net
Conventions for using CoinEx.Net when working with the CoinEx cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the CoinEx 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.
xt-net
Conventions for using the XT.Net library when working with the XT cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the XT 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.