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/zircote/rlm-rs/copilot-instructionsgit clone --depth 1 https://github.com/zircote/rlm-rsWrote 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/zircote/rlm-rs/copilot-instructions)<a href="https://agentmods.dev/instructions/zircote/rlm-rs/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/zircote/rlm-rs/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.01318 | $0.01318 |
| Opus 5 | $0.00659 | $0.00659 |
| Sonnet 5 | $0.00264 | $0.00264 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
rlm-rs 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- subcog copilot-instructions.md — 92% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
This document provides context for GitHub Copilot when working with this Rust project.
Project Context
This is a Rust crate using modern tooling:
- Rust: 1.95+ (2024 edition)
- Build System: Cargo
- Linting: clippy with pedantic and nursery lints
- Formatting: rustfmt
- Testing: Built-in test framework + proptest
- Supply Chain Security: cargo-deny
Code Generation Guidelines
Error Handling
Use Result types instead of panicking:
// Good - Returns Result
pub fn parse_value(input: &str) -> Result<i64, ParseError> {
input.parse().map_err(|e| ParseError::InvalidFormat(e))
}
// Avoid - Panics on failure
pub fn parse_value(input: &str) -> i64 {
input.parse().unwrap() // Never do this
}
Use thiserror for custom error types:
use thiserror::Error;
#[derive(Error, Debug)]
pub enum AppError {
#[error("invalid input: {0}")]
InvalidInput(String),
#[error("operation failed: {operation}")]
OperationFailed { operation: String },
#[error(transparent)]
Io(#[from] std::io::Error),
}
Type Annotations
Provide explicit return types for public functions:
// Good - explicit return type
pub fn process_data(items: &[String]) -> Vec<ProcessedItem> {
// implementation
}
// Avoid for public APIs
pub fn process_data(items: &[String]) -> impl Iterator<Item = ProcessedItem> {
// implementation
}
Documentation
Use doc comments with examples:
/// Processes a list of items according to the given configuration.
///
/// # Arguments
///
/// * `items` - The items to process.
/// * `config` - Configuration options for processing.
///
/// # Returns
///
/// A vector of processed items.
///
/// # Errors
///
/// Returns [`Error::InvalidInput`] if any item is invalid.
///
/// # Examples
///
/// ```rust
/// use rlm_rs::{process, Config};
///
/// let items = vec!["a", "b", "c"];
/// let config = Config::default();
/// let result = process(&items, &config)?;
/// # Ok::<(), rlm_rs::Error>(())
/// ```
pub fn process(items: &[&str], config: &Config) -> Result<Vec<Item>> {
// implementation
}
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 · 270 lines · 1,318 tokens per session scan A 11d5489af7e3
rlm-rs copilot-instructions.md is an instructions file published in the GitHub repository zircote/rlm-rs (57 stars, last pushed 3d ago), licensed MIT. It adds 1,318 tokens to every session, about $0.0066 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
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).