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/copilot-instructionsgit clone --depth 1 https://github.com/EthanAlgoX/LLM-TradeBotWrote 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/ethanalgox/llm-tradebot/copilot-instructions)<a href="https://agentmods.dev/instructions/ethanalgox/llm-tradebot/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ethanalgox/llm-tradebot/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 | $0.00809 | $0.00809 |
| Opus 5 | $0.00404 | $0.00404 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
LLM-TradeBot 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 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Instructions
Canonical source: AGENTS.md.
If any instruction in this file conflicts with AGENTS.md, follow AGENTS.md.
Core Rules
- Respect directory boundaries:
- Backend:
src/,data_provider/,api/,bot/ - Web:
apps/dsa-web/ - Desktop:
apps/dsa-desktop/ - Deployment/workflows:
scripts/,.github/workflows/,docker/
- Backend:
- Do not run
git commit,git tag, orgit pushwithout explicit user confirmation. - Before creating/updating PRs, PR review, or issue analysis, refresh the latest code baseline with
git fetch --all --prune; if the worktree is clean and the current branch can fast-forward, rungit pull --ff-only. If local changes, conflicts, missing upstream, or non-fast-forward history make that unsafe, do not stash/reset/overwrite local state; analyze against fetched remote refs or record the baseline gap before proceeding. - PR titles should use
<type>: <change summary>such asfix: 修复大盘分析历史记录丢失; usefix/feat/refactor/docs/chore/test/ciwhere possible, and avoid[codex],codex,autocode,copilot, or other tool/agent source prefixes. Treat this as process guidance and do not use title format mismatches as a hard review blocker. - Do not hardcode secrets, accounts, ports, model names, absolute environment-specific paths, or environment-specific branches.
- Reuse existing modules, configuration entrypoints, scripts, and tests instead of adding parallel implementations.
- For user-visible behavior changes, CLI/API changes, deployment changes, notification changes, or report-structure changes, update the relevant docs and
docs/CHANGELOG.md. - In
docs/CHANGELOG.md, the[Unreleased]section uses a flat format: one line per entry formatted as- [type] description, where type is one of新功能/改进/修复/文档/测试/chore. Do not add### category headersinside[Unreleased]to minimize merge conflicts in concurrent PRs. A maintainer will reorganize into the full categorized format at release time. - Use
README.mdonly for project positioning, high-level capabilities, quick start, main entrypoints, and sponsorship/cooperation information; avoid updating README unless the change is homepage-level. - Put detailed module behavior, page interaction, topic configuration, troubleshooting, field contracts, implementation semantics, and edge cases in the appropriate
docs/*.mdfile instead of README. - When config semantics change, sync
.env.exampleand assess impact on local runs, Docker, GitHub Actions, API, Web, and Desktop.
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 · 39 lines · 809 tokens per session scan A d0f227627f8b
LLM-TradeBot copilot-instructions.md is an instructions file published in the GitHub repository EthanAlgoX/LLM-TradeBot (316 stars, last pushed today), licensed MIT. It adds 809 tokens to every session, about $0.0040 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.
nautilus_AItrader AGENTS.md
AGENTS.md instructions for Patrick-code-Bot/nautilus_AItrader, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
ai-fund CLAUDE.md
Claude Code instructions for cubexch/ai-fund, covering ai fund, project structure, architecture, development workflow and ci/cd.
my-binance AGENTS.md
AGENTS.md instructions for cokepoppy/my-binance, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
jesse AGENTS.md
AGENTS.md instructions for jesse-ai/jesse, covering jesse repository guide for ai agents, skills, key characteristics, central framework and technology stack.