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/avids2/memorix/gemini-mdgit clone --depth 1 https://github.com/AVIDS2/memorixWhat 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.00846 | $0.00846 |
| Opus 5 | $0.00423 | $0.00423 |
| Sonnet 5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
memorix 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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memorix - Cross-Agent Memory Rules
Memorix is an open-source cross-agent memory layer for coding agents via MCP. These rules help Gemini-family agents share project-aware memory with the rest of the Memorix ecosystem.
You have access to Memorix memory tools. Follow these rules to maintain persistent, project-aware context across sessions.
Session Start - Bind Project, Then Load Context
At the beginning of every conversation, before responding to the user:
- Call
memorix_session_start. - If you are connected to the HTTP control-plane mode (normally started with
memorix background start;memorix serve-httpis the foreground variant) and you know the current workspace path, pass:agentprojectRoot= the absolute path of the current workspace or repo root
- If you are using stdio / Quick Mode and Memorix is already project-bound, calling
memorix_session_startwithoutprojectRootis acceptable. - If session start reports that the project could not be resolved, retry with the correct absolute workspace path before using project-scoped memory tools.
- Then call
memorix_searchwith a query related to the user's first message or the current project. - If results matter, use
memorix_detailto fetch the most relevant memories. - Reference relevant memories naturally so the user feels continuity.
Important:
projectRootis a detection anchor only; Git remains the source of truth for project identity.- In HTTP control-plane mode, explicit
projectRootbinding is the safest way to avoid cross-project drift.
During Session - Capture Important Context
Proactively call memorix_store whenever any of the following happen:
Architecture & Decisions
- Technology choice, framework selection, or design pattern adopted
- Trade-off discussion with a clear conclusion
- API design, database schema, or project structure decisions
Bug Fixes & Problem Solving
- A bug is identified and resolved - store root cause + fix
- Workaround applied for a known issue
- Performance issue diagnosed and optimized
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.
- 3d ago First seen · 86 lines · 846 tokens per session scan A 6ba00c3f9cec
memorix GEMINI.md is an instructions file published in the GitHub repository AVIDS2/memorix (705 stars, last pushed 3d ago), licensed Apache-2.0. It adds 846 tokens to every session, about $0.0042 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
mcp-server-azure-devops copilot-instructions.md
Instructions for Tiberriver256/mcp-server-azure-devops, covering azure devops mcp server - development instructions, prerequisites, building and running, 1. install dependencies and 2. build the server.
mcp-server-azure-devops AGENTS.md
Instructions for Tiberriver256/mcp-server-azure-devops: /home/tiberriver256/repos/mcp-server-azure-devops/docs/important-knowledge/azure-devops-rest-api-research.md Researching Azure DevOps REST APIs, selecting api-version, or handling Azure DevOps Server (on-prem) endpoints.
rosetta AGENTS.md
Instructions for griddynamics/rosetta: Main goal: cover E2E AI PDLC engineering workflows at foundation level for AI-First SDLC in enterprise. Top-level or orchestrator agents MUST READ docs/ARCHITECTURE.md contains technical details and guidance, and docs/CONTEXT.md - business context. Subagents - when needed.…
Ctxo CLAUDE.md
Instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).
draft CLAUDE.md
Instructions for drafthq/draft, covering claude.md, repository overview, build & test commands, run a single test and etc. — any test in tests/ is independently executable.
specops CLAUDE.md
Instructions for sanmak/specops, covering claude.md, what is specops, build & validate commands, run all tests (single command) and generate for a single platform.