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 instructions/jkorf/cryptoclients.net/copilot-instructionsgit clone --depth 1 https://github.com/JKorf/CryptoClients.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/instructions/jkorf/cryptoclients.net/copilot-instructions)<a href="https://agentmods.dev/instructions/jkorf/cryptoclients.net/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jkorf/cryptoclients.net/copilot-instructions.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.1 | $0.00700 | $0.00700 |
| Opus 5 | $0.00350 | $0.00350 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
CryptoClients.Net copilot-instructions.md 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for CryptoClients.Net
This repository is CryptoClients.Net, a C#/.NET aggregate client library for multiple cryptocurrency exchange APIs. It is part of the CryptoExchange.Net ecosystem.
When generating code that consumes CryptoClients.Net, follow these conventions.
Use CryptoClients.Net for multi-exchange workflows
Do not generate raw HttpClient calls to exchange endpoints. Use ExchangeRestClient, ExchangeSocketClient, shared API interfaces, or the exchange-specific clients exposed from the aggregate clients.
Client setup
using CryptoClients.Net;
using CryptoClients.Net.Interfaces;
using CryptoExchange.Net.SharedApis;
IExchangeRestClient restClient = new ExchangeRestClient();
IExchangeSocketClient socketClient = new ExchangeSocketClient();
For services, prefer services.AddCryptoClients(...) and inject IExchangeRestClient, IExchangeSocketClient, IExchangeOrderBookFactory, IExchangeTrackerFactory, or IExchangeUserClientProvider.
Result handling
Aggregate REST calls return ExchangeWebResult<T> or arrays of them. Socket subscriptions return ExchangeResult<UpdateSubscription> or arrays of them. Always check .Success before reading .Data.
API structure
restClient.GetSpotTickerAsync(...)and similar aggregate methods query one or more exchanges through shared APIs.restClient.GetSpotTickerClient("Binance")and similar helpers return a shared client interface for a specific exchange when supported.restClient.Binance,restClient.Kucoin,restClient.OKX, etc. expose the full exchange-specific REST clients.socketClient.SubscribeToTickerUpdatesAsync(...)and similar methods subscribe on one or more exchanges.socketClient.Binance,socketClient.Kucoin,socketClient.OKX, etc. expose the full exchange-specific socket clients.
Shared symbols
Use SharedSymbol, not hardcoded exchange symbol formats, when using aggregate or shared API methods:
var symbol = new SharedSymbol(TradingMode.Spot, "BTC", SharedSymbol.UsdOrStable);
var ticker = await restClient.GetSpotTickerAsync("Binance", new GetTickerRequest(symbol));
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.
- 5d ago First seen · 67 lines · 700 tokens per session scan A 6bc0876259f0
CryptoClients.Net copilot-instructions.md is an instructions file published in the GitHub repository JKorf/CryptoClients.Net (45 stars, last pushed 4d ago), licensed MIT. It adds 700 tokens to every session, about $0.0035 per session on Opus 5. 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 instructions, from other repositories
binance-net
Use Binance.Net when generating C#/.NET code that interacts with the Binance cryptocurrency exchange — including Spot, Margin, USD-M Futures, COIN-M Futures, Options, sub-accounts, brokerage, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on any request…
Binance.Net copilot-instructions.md
Copilot instructions for JKorf/Binance.Net, covering copilot instructions for binance.net, use binance.net, not raw http, client setup, result handling and api structure.
bybit-net
Use Bybit.Net when generating C#/.NET code that interacts with the Bybit cryptocurrency exchange, including V5 REST endpoints, V5 WebSocket subscriptions, unified accounts, spot, linear/inverse derivatives, options, spread trading, sub-accounts, account management, market data, and order placement. Triggers on…
Bybit.Net copilot-instructions.md
Copilot instructions for JKorf/Bybit.Net, covering copilot instructions for bybit.net, use bybit.net, not raw http, client setup, result handling and v5 api structure.
bingx-net
Use BingX.Net when generating C#/.NET code that interacts with BingX, including Spot, Perpetual Futures, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on BingX integration requests in C#, .NET, dotnet, F#, or VB.NET context.
kucoin-net
Use Kucoin.Net when generating C#/.NET code that interacts with the Kucoin cryptocurrency exchange API, including Spot, Margin, High Frequency spot trading, Futures, Unified Account, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on any request mentioning Kucoin…