Borrowing it
Nothing to install: this file belongs to skynetcmd/m3-memory. 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/skynetcmd/m3-memory/main/GEMINI.mdgit clone --depth 1 https://github.com/skynetcmd/m3-memoryWrote 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/skynetcmd/m3-memory/gemini-md)<a href="https://agentmods.dev/instructions/skynetcmd/m3-memory/gemini-md"><img src="https://agentmods.dev/badge/instructions/skynetcmd/m3-memory/gemini-md/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/skynetcmd/m3-memory/gemini-md"><img src="https://agentmods.dev/badge/instructions/skynetcmd/m3-memory/gemini-md.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.00856 | $0.00856 |
| Opus 5.5 | $0.00342 | $0.00342 |
| Sonnet 5.5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
m3-memory GEMINI.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 yesterday.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using m3 Memory
Tool names and signatures come from the MCP tool list. This is the part that isn't in a tool description: the protocol, and the traps.
Trust order
m3 memory > artifacts (git, handoff files) > session context. When m3 contradicts what you think you remember, trust m3 — context degrades across session boundaries, memory does not.
Verify capture is live
Registered ≠ working. The server can be connected while chatlog capture is
silently dead. Call m3_call("chatlog_status") once early in a substantive session. If
hooks are off or last_write is null/stale, say so loudly and don't proceed
silently — a dead chatlog means this session's decisions vanish at the next
session boundary. Never degrade quietly to flat files.
Protocol
- Search first.
memory_searchbefore re-deriving anything about this user, project, or machine. A settled decision re-litigated is a bug reintroduced. - Grade what you used. After answering with retrieved memories, grade them
once:
m3_call("memory_grade", {"grades": [{"memory_id": "<id>", "verdict": "helpful"}, ...]})—helpfulif you relied on it,unhelpfulif it was shown but did not help.memory_searchlists the ids ingrade_with. - Write as you go. If it took effort to learn and will matter later,
memory_writeit — decisions, corrections, runbooks, preferences. - Update, don't duplicate. Search before writing; prefer
memory_updateormemory_supersede(retires the old claim with asupersedesedge, keeps history) over a near-duplicate. Duplicates degrade later retrieval. - Link. Reference related memories as
[[name]]somemory_graphtraversal stays useful.
Chat log
Captured turns from host agents live in a store separate from curated memory.
Reach them with chatlog_search, chatlog_list_conversations, and
chatlog_promote (promotes turns into curated memory).
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.
- yesterday Changed · +55 lines · +544 tokens per session f2f90a8091f5
- 1mo ago First seen · 15 lines · 312 tokens per session scan A 6a135e01c6df
m3-memory GEMINI.md is an instructions file published in the GitHub repository skynetcmd/m3-memory (29 stars, last pushed yesterday), licensed Apache-2.0. It adds 856 tokens to every session, about $0.0034 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-08-30.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.