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/rust-lsp/copilot-instructionsgit clone --depth 1 https://github.com/zircote/rust-lspWhat 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.00226 | $0.00226 |
| Opus 5 | $0.00113 | $0.00113 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
rust-lsp 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.
What it actually says
Copilot instructions
You are working in a Claude Code plugin for Rust development with LSP and automated hooks.
Priorities
- Keep changes small and reviewable.
- Hooks must be fast and fail-open (use
|| true). - Update README.md and commands/setup.md when changing user-facing behavior.
Key Files
.lsp.json- rust-analyzer LSP configurationhooks/hooks.json- 18 automated development hookscommands/setup.md-/setupcommand for toolchain installation
Commands
- Setup:
/setup(installs rust-analyzer and all cargo tools) - Manual install: See
commands/setup.mdfor the full toolchain
When Adding Hooks
Use this pattern in hooks/hooks.json:
{
"name": "hook-name",
"event": "afterWrite",
"hooks": [{ "type": "command", "command": "command -v tool && tool args | head -N || true" }],
"matcher": "**/*.rs"
}
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 · 34 lines · 226 tokens per session scan A 33b03084fdfc
rust-lsp copilot-instructions.md is an instructions file published in the GitHub repository zircote/rust-lsp (12 stars, last pushed 22d ago), licensed MIT. It adds 226 tokens to every session, about $0.0011 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
rust-doctor AGENTS.md
Instructions for arthjean/rust-doctor, covering agents.md, trust boundary, commands, running the tool on this repository and the subsystems.
rust-doctor CLAUDE.md
Instructions for arthjean/rust-doctor, a project described as: Your agent writes bad Rust. This catches it.
brooks-lint AGENTS.md
AGENTS.md instructions for hyhmrright/brooks-lint, covering agents.md, core purpose, skill integration, engineering standards and project structure.
vibeguard AGENTS.md
Instructions for majiayu000/vibeguard, covering agent instructions, scope, start here, core rules and delivery policy.
logic-lens GEMINI.md
Instructions for hyhmrright/logic-lens, covering logic-lens — developer guide (gemini cli), invoking skills, installation, project layout and key conventions.
yocto-lens AGENTS.md
Instructions for prashantdivate/yocto-lens: You are working on Yocto Lens, a Go static analysis tool for Yocto Project and OpenEmbedded metadata.