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/ethanalgox/llm-tradebot/backendgit clone --depth 1 https://github.com/EthanAlgoX/LLM-TradeBotWhat 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.00176 | $0.00176 |
| Opus 5 | $0.00088 | $0.00088 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
LLM-TradeBot backend.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 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.
What it actually says
Backend Instructions
- Preserve current pipeline boundaries and reuse existing services, repositories, schemas, and fallback logic instead of creating parallel paths.
- Changes touching config, CLI flags, schedule semantics, API behavior, auth, or report payloads must sync
.env.exampleand assess Web/Desktop compatibility. - Changes in
data_provider/must preserve provider priority, normalization behavior, timeout/retry expectations, and graceful degradation. - Prefer
./scripts/ci_gate.shwhen feasible; otherwise runpython -m py_compileon changed files plus the closest deterministic tests. - Do not let a single provider, notification channel, or optional integration failure break the main analysis flow unless the requirement explicitly demands fail-fast behavior.
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.
- 2d ago First seen · 12 lines · 176 tokens per session scan A 0d01c998fd8d
LLM-TradeBot backend.instructions.md is an instructions file published in the GitHub repository EthanAlgoX/LLM-TradeBot (316 stars, last pushed 14d ago), licensed MIT. It adds 176 tokens to every session, about $0.0009 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
Instructions for JKorf/Binance.Net, covering copilot instructions for binance.net, use binance.net, not raw http, client setup, result handling and api structure.
tradecat-public AGENTS.md
Instructions for tradecatlabs/tradecat-public, covering tradecat-public agent 操作手册, mission & scope, golden path, must-run commands and code change rules.
Kucoin.Net copilot-instructions.md
Instructions for JKorf/Kucoin.Net, covering copilot instructions for kucoin.net, use kucoin.net, not raw http, client setup, result handling and api structure.
crypto-clients-net
Use CryptoClients.Net when generating C#/.NET code that needs unified access to multiple cryptocurrency exchanges, aggregate REST requests, multi-exchange WebSocket subscriptions, shared CryptoExchange.Net APIs, cross-exchange order books, trackers, dynamic exchange credentials, or direct access to any bundled…
crypto-trading-arena CLAUDE.md
Instructions for ryan-yuuu/crypto-trading-arena, covering crypto trading arena development guide for dummies, dependency management and development environment, architecture, conventions and sub-agents.