What is memoria AGENTS.md?

Project instructions for Memoria that require using GitNexus, a code-understanding tool, to inspect relationships between code symbols and execution flows. They describe checks to perform before editing and committing code, plus guidance for debugging and refactoring.

Use them when working on the Memoria repository to assess change impact, navigate unfamiliar code, and check that edits affected only expected areas.

They help reveal which callers and processes may be affected by a change before code is modified.

How ivkond/memoria configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to ivkond/memoria. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ivkond/memoria/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ivkond/memoria

Made for: Claude Code, Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ivkond/memoria/agents-md/github.svg)](https://agentmods.dev/instructions/ivkond/memoria/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/ivkond/memoria/agents-md"><img src="https://agentmods.dev/badge/instructions/ivkond/memoria/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ivkond/memoria/agents-md"><img src="https://agentmods.dev/badge/instructions/ivkond/memoria/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,400 This file is loaded in full into every session.

When invoked 1,400 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 80% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.01400	$0.01400
Opus 5.5	$0.00560	$0.00560
Sonnet 5.5	$0.00280	$0.00280
Haiku 4.5	$0.00140	$0.00140

Measured 2mo ago against content hash 3d0c5adbeb29, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memoria 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 2mo 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.

Origin

This is a copy

80% identical to claude-code-trace AGENTS.md — 113 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitNexus — Code Intelligence

This project is indexed by GitNexus as memoria (274 symbols, 660 relationships, 22 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run npx gitnexus analyze in terminal first.

Always Do

MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
When exploring unfamiliar code, use gitnexus_query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use gitnexus_context({name: "symbolName"}).

When Debugging

gitnexus_query({query: "<error or symptom>"}) — find execution flows related to the issue
gitnexus_context({name: "<suspect function>"}) — see all callers, callees, and process participation
READ gitnexus://repo/memoria/process/{processName} — trace the full execution flow step by step
For regressions: gitnexus_detect_changes({scope: "compare", base_ref: "main"}) — see what your branch changed

When Refactoring

Renaming: MUST use gitnexus_rename({symbol_name: "old", new_name: "new", dry_run: true}) first. Review the preview — graph edits are safe, text_search edits need manual review. Then run with dry_run: false.
Extracting/Splitting: MUST run gitnexus_context({name: "target"}) to see all incoming/outgoing refs, then gitnexus_impact({target: "target", direction: "upstream"}) to find all external callers before moving code.
After any refactor: run gitnexus_detect_changes({scope: "all"}) to verify only expected files changed.

Read the full file on GitHub · 102 lines

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.

2mo ago First seen · 102 lines · 1,400 tokens per session scan A 3d0c5adbeb29

Subscribe to this mod's changes

memoria AGENTS.md is an instructions file published in the GitHub repository ivkond/memoria (0 stars, last pushed 6mo ago), licensed MIT. It adds 1,400 tokens to every session, about $0.0056 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to claude-code-trace AGENTS.md, differing in 113 lines, and is treated as a copy.

fastmcp mcp mem0 memgraph model-context-protocol

memoria AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
memoria AGENTS.mdivkond/memoria	Instructions file	0	6mo ago	MIT	A	1,400	Claude Code, Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

memoria: Instructions file for Claude Code