Borrowing it
Nothing to install: this file belongs to Hessesian/kmp-lsp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Hessesian/kmp-lsp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Hessesian/kmp-lspWrote 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/hessesian/kmp-lsp/copilot-instructions)<a href="https://agentmods.dev/instructions/hessesian/kmp-lsp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/hessesian/kmp-lsp/copilot-instructions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/hessesian/kmp-lsp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/hessesian/kmp-lsp/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00914 | $0.00914 |
| Opus 5.5 | $0.00366 | $0.00366 |
| Sonnet 5.5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
kmp-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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kmp-lsp — Agent & Copilot Coding Instructions
Deep reference material (source layout, architecture patterns, coding guidelines with examples, test conventions, Serena MCP workflow) lives in docs/agent-reference.md. Load that on-demand. This file is behavioral rules only.
Workflow
- Never commit directly to
main. Always create a feature branch, push, and open a PR. - PR merge workflow: commit → push → resolve ALL review threads via
gh api graphql resolveReviewThread→ re-request review →gh pr merge --squash --delete-branch. - Stacked PRs: merge base first, rebase dependent, then
cargo build && cargo teston main after. - After merging, install the binary:
cargo install --path . --force. - Run tests after every change:
cargo test. All tests must pass. - Run clippy after every change:
cargo clippy -- -D warnings. Must be clean.
Code Quality
- Rust types model behaviour — code should be obvious in retrospect.
- Reach for a type before reaching for a comment. When you feel the need to explain control flow — why a fallback exists, what a
None/empty result means, which order branches run, whether a string is still a placeholder — first ask whether an enum, newtype, or struct would encode that meaning so the compiler carries it and the signature tells the story. Preferenum Outcome { Resolved(T), KeepWalking }overOption<T>+ a comment; prefer aResolvedTypethat distinguishes concrete vs. generic over anis_generic(&str)sniff. Keep comments for irreducible domain knowledge (e.g. whyapplymeansthis= receiver), not for scaffolding the types should hold. - No abbreviated names. Never use single-letter or short variable names like
s,c,ty,rt,sym,loc,p,diags. Use full words:string,char,type,receiver,symbol,location,package,diagnostics. - Explicit over clever. Split compound boolean expressions into named variables. Avoid chained combinators when a simple conditional is clearer.
- Every fix must include a test. If a bug slips through, the test should have caught it.
- Write tests that prove correctness, not just verify happy-path. Include competing/misleading definitions to catch regressions.
andin a function name means it's doing two things. Split into two functions.- Section comments inside a function body signal a split. Each phase becomes a named helper.
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.
- 1mo ago First seen · 46 lines · 914 tokens per session scan A f4d4b449a571
kmp-lsp copilot-instructions.md is an instructions file published in the GitHub repository Hessesian/kmp-lsp (201 stars, last pushed 2d ago), licensed MIT. It adds 914 tokens to every session, about $0.0037 per session on Opus 5.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-09-04.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.