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/vaiz/rust-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/Vaiz/rust-mcp-serverWhat 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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
rust-mcp-server 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 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for Rust MCP Server
This is a Rust implementation of a Model Context Protocol (MCP) server.
Project Context
- Language: Rust
- Protocol: Model Context Protocol (MCP)
- Communication: JSON-RPC over stdio
- Architecture: Async/await with Tokio runtime
Key Guidelines
- Follow Rust best practices and idioms
- Use proper error handling with
Result<T, E>andohno::AppErrorfor error propagation - Implement MCP protocol methods according to the specification
- Use structured logging with the
tracingcrate - Ensure all async operations are properly awaited
MCP Protocol Implementation
- Initialize: Handle client initialization and capability negotiation
- Tools: Implement tool listing and execution
- Resources: Handle resource discovery and reading
- Logging: Support MCP logging protocol
Dependencies
tokio: Async runtimeserde: Serialization/deserializationrmcp: MCP protocol handlingohno: Error handlingtracing: Structured logging
AI Agent Guidelines
1. Always Use Rust MCP Tools
- Use
#cargo-checkfor quick code validation - Use
#cargo-clippyfor linting - Use
#cargo-fmtfor code formatting - Use
#cargo-testfor running tests
2. use @rust-docs subagent
- For any questions about public API for dependencies or standard library, consult the
@rust-docssubagent. Just ask it what you looking for in natural language, and it will fetch the relevant documentation for you.
2. Development Workflow
Follow this systematic approach when working on code changes:
- Check current state: Use
#cargo-checkwithall_targets: true, all_features: true - Make changes: Edit code using appropriate development tools
- Validate: Use
#cargo-clippywithworkspace: true, all_targets: true - Format: Use
#cargo-fmtwithall: true - Test: Use
#cargo-testwithall_features: true - Build: Use
#cargo-buildwithall_targets: true, all_features: truefor final verification - Check unused dependencies: Use
#cargo-macheteto identify unused dependencies - Verify security compliance: Use
#cargo-deny-checkto ensure security and licensing compliance
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 · 72 lines · 691 tokens per session scan A 536319f210ea
rust-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository Vaiz/rust-mcp-server (35 stars, last pushed 17d ago), licensed Unlicense. It adds 691 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
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
terminal-browser AGENTS.md
AGENTS.md instructions for zenbu-labs/terminal-browser, a project described as: A browser inside your terminal.
mq commit.instructions.md
Instructions for harehare/mq: Use the following format for commit messages.
openapi AGENTS.md
Instructions for longbridge/openapi, covering agent guidelines, after modifying rust code, after modifying the node.js sdk (nodejs/), after modifying the python sdk api (python/) and after modifying the c sdk (c/).
playwright-rust CLAUDE.md
Instructions for padamson/playwright-rust, covering claude.md, project, repository layout, skills (procedural reference) and documentation hierarchy.
flox AGENTS.md
AGENTS.md instructions for flox/flox, covering claude.md, project overview, development setup, already in dev shell (innixshell is set) — run directly and not in dev shell — wrap with nix develop -c.