copilot-memory-mcp copilot-instructions.md

Instructions for using a persistent memory service with GitHub Copilot. The service stores and retrieves project decisions, conventions, findings, and other selected notes through an MCP server.

In plain words
What is it for?
Guiding memory searches before architecture questions and memory updates after important decisions or workarounds. They specify project names and categories to use for stored memories.
Why use it?
They help the assistant recall earlier architecture decisions and conventions instead of answering from incomplete context. They also define when to save, update, search, or remove memories.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/labforgedev/copilot-memory-mcp/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/LabForgeDev/copilot-memory-mcp

Made for: GitHub Copilot.

Per session 259 This file is loaded in full into every session.
When invoked 259 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00259 $0.00259
Opus 5 $0.00130 $0.00130
Sonnet 5 $0.00052 $0.00052
Haiku 4.5 $0.00026 $0.00026

Measured 3d ago against content hash e17fb5b90087, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

copilot-memory-mcp 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.

examples/.github/copilot-instructions.md · 23 lines

What it actually says

GitHub Copilot Instructions — Memory Tools

You have access to a persistent memory MCP server (copilot-memory) at http://localhost:8000/sse.

Available tools

Tool When to use
create_memory Save a new decision, convention, or finding
search_memories Retrieve relevant context before answering
update_memory Amend an existing memory when something changes
delete_memory Remove stale or incorrect memories
list_memories Browse all saved memories for a project

Rules

  1. Always search before answering questions about architecture, conventions, or past decisions — call search_memories first.
  2. Always save new architectural decisions, agreed conventions, and non-obvious workarounds.
  3. Set project_name to the current repository name on every call.
  4. Prefer update_memory over delete + recreate when content changes.
  5. Use consistent tags: architecture, convention, bug, performance, devops, security, testing, tooling.
  6. Do not save temporary debug notes or information already obvious from the code.
Changes

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.

  1. 3d ago First seen · 23 lines · 259 tokens per session scan A e17fb5b90087

Subscribe to this mod's changes

copilot-memory-mcp copilot-instructions.md is an instructions file published in the GitHub repository LabForgeDev/copilot-memory-mcp (3 stars, last pushed 5mo ago), licensed MIT. It adds 259 tokens to every session, about $0.0013 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-31.

Related

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).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens