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/lukaszhao/memory-inheritance/copilot-instructionsgit clone --depth 1 https://github.com/LukasZhao/memory-inheritanceWhat 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.00154 | $0.00154 |
| Opus 5 | $0.00077 | $0.00077 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
memory-inheritance 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
GitHub Copilot Instructions
This repository uses Memory Inheritance.
Required Context
Before making changes, read:
PROJECT_MEMORY.md
PROJECT_MEMORY.md is the compact canonical project memory for this codebase.
Token-aware Reading Rule
Do not load every file under .memory/ by default.
If more detail is needed, consult:
.memory/index.json
Then read only the referenced memory files relevant to the current task.
Prioritize references with higher criticality scores when context is limited.
Rules
- Treat adapter files as routing instructions, not project memory stores.
- Preserve manual notes in
PROJECT_MEMORY.md. - Keep changes focused and consistent with the project memory.
- Do not delete memory references unless explicitly requested.
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 · 27 lines · 154 tokens per session scan A 518408800bd3
memory-inheritance copilot-instructions.md is an instructions file published in the GitHub repository LukasZhao/memory-inheritance (2 stars, last pushed 3mo ago), licensed MIT. It adds 154 tokens to every session, about $0.0008 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.
Other instructions, from other repositories
cocoindex AGENTS.md
AGENTS.md instructions for cocoindex-io/cocoindex, covering agents.md, build and test commands, building, testing and code formatting and linting.
apm architecture.instructions.md
Single canonical owner discipline: one authority per durable decision, guarded by a regression test + a static boundary check.
apm python.instructions.md
Python development guidelines.
framework AGENTS.md
Instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
packmind packmind-frontend-error-management.instructions.md
Instructions for PackmindHub/packmind: A global error boundary is already configured at the root level (in root.tsx) that automatically catches all page crashes, 404s, and loader failures. This standard defines when and how to use explicit... .
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.