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/lsp-tools/copilot-instructionsgit clone --depth 1 https://github.com/zircote/lsp-toolsWhat 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.00292 | $0.00292 |
| Opus 5 | $0.00146 | $0.00146 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
lsp-tools 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 3d 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 LSP-first code intelligence with strong enforcement patterns.
Priorities
- Keep changes small and reviewable.
- Update README.md and CHANGELOG.md when changing user-facing behavior.
- Maintain the Three Iron Laws enforcement in SKILL.md.
Key Files
.claude-plugin/plugin.json- Plugin manifestcommands/lsp-setup.md-/lsp-setupcommand for project configurationskills/lsp-enable/SKILL.md- Main enforcement skill with Three Iron Lawsskills/lsp-enable/references/- Per-language LSP sections and hooks
Commands
- Setup:
/lsp-tools:lsp-setup(configures hooks and CLAUDE.md for detected languages) - Verify:
/lsp-tools:lsp-setup --verify-only(checks LSP server status)
When Adding Language Support
- Create
references/{language}-lsp-section.mdwith CLAUDE.md guidance - Create
references/{language}-hooks.jsonwith development hooks - Add installation scripts to
scripts/bash/andscripts/powershell/ - Update
lsp-server-registry.mdwith installation commands - Update
SETUP-GUIDE-ALL-LANGUAGES.md - Update README.md supported languages table
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.
- 3d ago First seen · 31 lines · 292 tokens per session scan A a296f6b295b6
lsp-tools copilot-instructions.md is an instructions file published in the GitHub repository zircote/lsp-tools (12 stars, last pushed 23d ago), licensed MIT. It adds 292 tokens to every session, about $0.0015 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
repobrain copilot-instructions.md
Copilot instructions for study8677/repobrain, covering github copilot bootstrap instructions and hard rule — query the repobrain hub first.
repobrain AGENTS.md
AGENTS.md instructions for study8677/repobrain: Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules.…
Ctxo CLAUDE.md
Instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).
trace-mcp AGENTS.md
Instructions for nikolai-vysotskyi/trace-mcp: IMPORTANT: For ANY code exploration task, ALWAYS use trace-mcp tools first. NEVER use Read/Grep/Glob/Bash(ls,find) for navigating source code.
sverklo CLAUDE.md
Instructions for sverklo/sverklo, covering sverklo development, using sverklo tools, project structure and build & test.
codesage AGENTS.md
Instructions for iliaal/codesage, covering codesage, build, sanity check before pushing, crate map and search pipeline.