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/governancegit 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/governance)<a href="https://agentmods.dev/instructions/ethanalgox/llm-tradebot/governance"><img src="https://agentmods.dev/badge/instructions/ethanalgox/llm-tradebot/governance.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.00423 | $0.00423 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
LLM-TradeBot governance.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.
What it actually says
Governance Instructions
- Keep commands, file paths, workflow names, config keys, release paths, and directory references aligned with the executable repository state.
AGENTS.mdis the canonical AI collaboration document; if its meaning changes, syncCLAUDE.md,.github/copilot-instructions.md,.github/instructions/*.instructions.md, and repository skills as needed.- Root
SKILL.mdanddocs/openclaw-skill-integration.mddescribe product or external integration behavior, not repository governance. - Explain which pipeline, release path, deployment path, review automation, or governance asset is affected and what the rollback path is.
- Before creating/updating PRs, PR review, or issue analysis, refresh the latest code baseline with
git fetch --all --prune; only rungit pull --ff-onlywhen the worktree is clean and the current branch can fast-forward. If not, keep local state intact and record the fetched remote baseline or branch gap before proceeding. - Keep
README.mdlimited to homepage-level content such as positioning, high-level capabilities, quick start, main entrypoints, and sponsorship/cooperation; put detailed behavior, configuration, troubleshooting, field contracts, and edge cases indocs/*.md. - Avoid widening permissions, secret exposure, or destructive automation without a clearly documented need.
- Preserve the repository's opt-in auto-tag behavior (
#patch,#minor,#major) unless the change explicitly updates release policy. - When creating, reviewing, or suggesting PRs, prefer PR titles in
<type>: <change summary>form and omit tool/agent source prefixes such as[codex],codex,autocode, orcopilot; treat this as non-blocking guidance, not a review hard blocker. - If only one language version of a document is updated, explain why the counterpart was not synchronized.
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 · 17 lines · 423 tokens per session scan A 4368a6dd58cc
LLM-TradeBot governance.instructions.md is an instructions file published in the GitHub repository EthanAlgoX/LLM-TradeBot (316 stars, last pushed yesterday), licensed MIT. It adds 423 tokens to every session, about $0.0021 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.
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.
polymarket-alpha-bot CLAUDE.md
Instructions for chainstacklabs/polymarket-alpha-bot, covering claude.md, commands, development, pipeline and seed data.
ohlcv CLAUDE.md
Claude Code instructions for Mario-SO/ohlcv, covering claude.md, project overview, build and development commands, core commands and build the library and demo.
luno-mcp copilot-instructions.md
Instructions for luno/luno-mcp, covering github copilot instructions, repository structure, coding standards, go standards and mcp server guidelines.