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/luno/luno-mcp/copilot-instructionsgit clone --depth 1 https://github.com/luno/luno-mcpWrote 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/luno/luno-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/luno/luno-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/luno/luno-mcp/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.00885 | $0.00885 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
luno-mcp 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
This document provides guidelines for using GitHub Copilot with the Luno MCP server. These instructions help Copilot understand our codebase structure, standards, and best practices.
Repository Structure
The Luno MCP repository follows a structured organization:
/cmd- contains main application entry points/server- main MCP server implementation
/internal- internal packages not meant for external use/config- configuration handling/resources- MCP resources implementation/server- server setup and initialization/tools- tools implementation for Luno API interaction/tests- testing utilities
Coding Standards
When generating code with Copilot, ensure it follows these principles:
Go Standards
- Follow Go idioms and best practices
- Use error handling with proper context
- Always either return errors or log them, but never both
- We very rarely should be ignoring errors. If we do, explicitly ignore it with
_ = - Implement interfaces only when needed
- Prefer simple, readable code over clever solutions
- Use the Go standard library when appropriate
- Don't worry about test files exceeding the cyclomatic complexity threshold
MCP Server Guidelines
- Follow the Model Context Protocol (MCP) standards
- Separate concerns between resources and tools
- Implement proper error handling and reporting
- Use the mcp-go library patterns correctly
- Ensure proper validation of inputs from clients
Tool Dependencies
Mockery
- Mockery is declared as a tool in the go.mod file, this means that instead of running the
mockerycommand, we run it asgo tool mockery - Use .EXPECT() rather than .On() for setting expectations in tests
Testing Requirements
- Write unit tests for all business logic
- Don't just write tests for the happy path, consider boundary/edge and error cases
- Tests should be deterministic whenever possible
- Always write table-driven tests
- Use spaces rather than
_s in test names - Structure test cases clearly with descriptive fields
- Use spaces rather than
- Test functions independently when possible to avoid external dependencies
- Use testify or standard library assertions to check results
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 · 101 lines · 885 tokens per session scan A b7f9b7b35372
luno-mcp copilot-instructions.md is an instructions file published in the GitHub repository luno/luno-mcp (25 stars, last pushed 9d ago), licensed MIT. It adds 885 tokens to every session, about $0.0044 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
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.
ccxt CLAUDE.md
Claude Code instructions for ccxt/ccxt, covering ccxt — repository guide for contributors and ai agents, 1. architecture, rest vs pro (websocket), per-language model and two transpilers.
binance-trading-bot AGENTS.md
AGENTS.md instructions for chrisleekr/binance-trading-bot, covering engineering charter, project, architecture principles, core invariants and stack.
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.
tradememory-protocol AGENTS.md
Instructions for mnemox-ai/tradememory-protocol, covering tradememory protocol — agent context, project rules, recent changes and current status.
LLM-TradeBot copilot-instructions.md
Copilot instructions for EthanAlgoX/LLM-TradeBot, covering repository instructions, core rules, validation and ai asset governance.