m3-memory GEMINI.md

m3-memory GEMINI.md is an instructions file for Gemini CLI from skynetcmd/m3-memory. It costs 312 tokens per session, scanned A, original, Apache-2.0.

Project instructions for skynetcmd/m3-memory, covering Git practices and where the system stores its persistent data, configuration, logs, and models.

In plain words
What is it for?
Use them when changing or pushing the project, relocating its state, checking tool-catalog updates, or working with the M3_MEMORY_ROOT setting.
Why use it?
They help contributors follow the repository’s required commit, hook, pre-push, catalog, and data-location rules.

Instructions file for Gemini CLI

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/skynetcmd/m3-memory/gemini-md
Clone the repo
git clone --depth 1 https://github.com/skynetcmd/m3-memory

Made for: Gemini CLI.

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

agentmods badge for m3-memory GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/skynetcmd/m3-memory/gemini-md.svg)](https://agentmods.dev/instructions/skynetcmd/m3-memory/gemini-md)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 312 This file is loaded in full into every session.
When invoked 312 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.00312 $0.00312
Opus 5 $0.00156 $0.00156
Sonnet 5 $0.00062 $0.00062
Haiku 4.5 $0.00031 $0.00031

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

Security

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 4d 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.

GEMINI.md · 15 lines

What it actually says

docs/AGENT_INSTRUCTIONS.md

Git Standards

  • Commit Messages: Do NOT include "Co-Authored-By" lines in commit messages. Focus on clear, concise descriptions of "why" and "what".
  • Pre-push process (MANDATORY, all agents): After cloning, run python bin/setup_hooks.py once to enable the shared pre-push gate. Before any push, the tool-catalog drift check (python bin/check_tool_catalog_drift.py) and bench-data leakage scan must pass. If you change bin/mcp_tool_catalog.py, regenerate the catalog/inventory and update the "N tools" counts in the same change. Full rationale: the "Pre-push process — ALL agents" section in docs/AGENT_INSTRUCTIONS.md. This is enforced by the local hook AND CI, not just convention.

Homecoming Architecture

  • Unified Root: All persistent state (databases, configs, logs, models) defaults to ~/.m3-memory/.
  • Environment Override: Use M3_MEMORY_ROOT to relocate the entire system state.
  • Data Location:
    • Databases: ~/.m3-memory/memory/*.db
    • Configs: ~/.m3-memory/memory/.chatlog_config.json, etc.
    • Security Salt: ~/.m3-memory/.agent_os_salt
  • Migration: Use bin/homecoming.py to relocate legacy repo-relative state to the new home root.
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. 4d ago First seen · 15 lines · 312 tokens per session scan A 6a135e01c6df

Subscribe to this mod's changes

m3-memory GEMINI.md is an instructions file published in the GitHub repository skynetcmd/m3-memory (23 stars, last pushed 4d ago), licensed Apache-2.0. It adds 312 tokens to every session, about $0.0016 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.