Borrowing it
Nothing to install: this file belongs to pi22by7/In-Memoria. 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/pi22by7/In-Memoria/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/pi22by7/In-MemoriaWrote 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/pi22by7/in-memoria/copilot-instructions)<a href="https://agentmods.dev/instructions/pi22by7/in-memoria/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/pi22by7/in-memoria/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.1 | $0.03037 | $0.03037 |
| Opus 5 | $0.01519 | $0.01519 |
| Sonnet 5 | $0.00607 | $0.00607 |
| Haiku 4.5 | $0.00304 | $0.00304 |
Grade A, and why
In-Memoria 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 6d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for In Memoria
This repository includes In Memoria, an intelligent MCP (Model Context Protocol) server that provides codebase intelligence through semantic analysis, pattern recognition, and smart navigation.
⚠️ CRITICAL: Path Parameter Usage
ALWAYS provide absolute paths to In-Memoria tools. NEVER rely on default values.
Why This Matters
In MCP server context, process.cwd() is unpredictable and may point to the wrong directory (like /home/user instead of your project). Always specify the path explicitly to avoid analyzing the wrong codebase or creating databases in unexpected locations.
// ❌ WRONG - May use incorrect directory
await use_mcp_tool('in-memoria', 'get_project_blueprint', {
includeFeatureMap: true
});
// ✅ CORRECT - Always specify path explicitly
await use_mcp_tool('in-memoria', 'get_project_blueprint', {
path: '/absolute/path/to/project', // Use workspace root
includeFeatureMap: true
});
Getting the Project Path
- In VS Code: Use
${workspaceFolder}or workspace root API - Ensure it's an absolute path (starts with
/on Unix,C:\on Windows) - Be consistent across all tool calls in a session
- Verify the path exists before calling tools
Path Convention for All Tools
Every tool that accepts a path parameter should receive:
- Absolute paths to the project root directory
- Same path throughout the entire session
- No relative paths like
.or./src(resolve them first)
Core Capabilities
In Memoria learns from codebases and provides:
- Instant project context - Tech stack, entry points, key directories, architecture overview
- Semantic search - Find code by meaning, not just keywords
- Pattern recognition - Discover coding patterns and best practices
- Smart file routing - Navigate to relevant files from vague requests
- Coding approach predictions - Get implementation suggestions based on learned patterns
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.
- 6d ago First seen · 368 lines · 3,037 tokens per session scan A d91e6900ad80
In-Memoria copilot-instructions.md is an instructions file published in the GitHub repository pi22by7/In-Memoria (172 stars, last pushed 8mo ago), licensed MIT. It adds 3,037 tokens to every session, about $0.0152 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
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.
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.
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).
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).
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.
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.