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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/skynetcmd/m3-memory/agents-md"><img src="https://agentmods.dev/badge/instructions/skynetcmd/m3-memory/agents-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/agents-md"><img src="https://agentmods.dev/badge/instructions/skynetcmd/m3-memory/agents-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.00509 | $0.00509 |
| Opus 5.5 | $0.00204 | $0.00204 |
| Sonnet 5.5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
m3-memory AGENTS.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 1mo 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 — 16 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.pyonce 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 changebin/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 indocs/AGENT_INSTRUCTIONS.md. This is enforced by the local hook AND CI, not just convention.
Homecoming Architecture
- Decoupled Roots: Persistent state is split across three roots so databases and configuration can be relocated and secured independently. All three are overridable via the matching env var.
- Data Location:
- Databases + runtime state —
M3_ENGINE_ROOT, default~/.m3/engine:agent_memory.db,agent_chatlog.db,files_database.db, chatlog spill,logs/ - Configs —
M3_CONFIG_ROOT, default~/.m3/config:.chatlog_config.json,.migrate_config.json,.agent_os_salt - Payload / repo clone —
M3_MEMORY_ROOT, default~/.m3-memory
- Databases + runtime state —
- Precedence:
M3_ENGINE_ROOT/M3_CONFIG_ROOT→M3_MEMORY_ROOT/{engine,config}→~/.m3/{engine,config}.M3_MEMORY_ROOTacts as a master override only when the specific vars are unset; a specific root always wins. Canonical implementation:get_m3_engine_root()/get_m3_config_root()inbin/m3_core/paths.py. - Split-brain hazard: the MCP server reads roots from its
envblock in client settings, while hooks inherit the client's process env. PinM3_ENGINE_ROOT+M3_CONFIG_ROOTin both or the server and the chatlog hook will write to different stores. - Migration: Use
bin/homecoming.pyto relocate legacy repo-relative state to the new home root.
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.
- 1mo ago First seen · 16 lines · 509 tokens per session scan A 312fc9eb1e22
m3-memory AGENTS.md is an instructions file published in the GitHub repository skynetcmd/m3-memory (29 stars, last pushed today), licensed Apache-2.0. It adds 509 tokens to every session, about $0.0020 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.
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.
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).