memorax-repo-memory

memorax-repo-memory is an agent for Claude Code from memorax-ai/memorax-code. It costs 20 tokens per session (387 once invoked), scanned A, original, MIT.

A narrowly controlled agent for building or updating repository memory for an exact MemoraX delegation ticket. Repository memory is a separate bundle of notes or metadata about a code repository and a delegated job.

In plain words
What is it for?
Use it to claim the specified delegation, update only the repository's memory bundle and required configuration, then finish or abort the ticket through the supplied helpers.
Why use it?
It enforces the supplied ticket and repository instructions, reducing the risk of changing source code or working on the wrong delegated task.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to claim the specified delegation, update only the repository's memory bundle and required configuration, then finish or abort the ticket through the supplied helpers.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/memorax-ai/memorax-code/memorax-repo-memory
About the project

MemoraX Code is a shared memory layer for AI coding agents that stores and recalls repository knowledge, engineering lessons, and working preferences across sessions. It helps developers avoid repeating context when working with Codex, Claude Code, and other supported agents. The catalogue entries provide hooks, instructions, skills, and a plugin for using MemoraX Code.

memorax-ai/memorax-code · 2,035 stars · on GitHub · code.memorax.net

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.

Clone the repo
git clone --depth 1 https://github.com/memorax-ai/memorax-code

Made for: Claude Code.

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 memorax-repo-memory

README.md
[![agentmods](https://agentmods.dev/badge/agents/memorax-ai/memorax-code/memorax-repo-memory/github.svg)](https://agentmods.dev/agents/memorax-ai/memorax-code/memorax-repo-memory)
Your own site
<a href="https://agentmods.dev/agents/memorax-ai/memorax-code/memorax-repo-memory"><img src="https://agentmods.dev/badge/agents/memorax-ai/memorax-code/memorax-repo-memory/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.

agentmods 80×15 button for memorax-repo-memory

Your own site · 80×15
<a href="https://agentmods.dev/agents/memorax-ai/memorax-code/memorax-repo-memory"><img src="https://agentmods.dev/badge/agents/memorax-ai/memorax-code/memorax-repo-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 387 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00020 $0.00387
Opus 5.5 $0.00008 $0.00155
Sonnet 5.5 $0.00004 $0.00077
Haiku 4.5 $0.00002 $0.00039

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

Security

Grade A, and why

memorax-repo-memory 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 10d 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.

packages/ts/memorax-code-cursor-adapter/agents/memorax-repo-memory.md · 34 lines

What it actually says

Maintain only the repository and job identified by the supplied MemoraX delegation. Use Cursor's normal tool permissions. Do not install or invoke a standalone agent CLI, change repository source files, or start another agent.

  1. Run the exact claim command supplied in the delegation, preserving its executable, helper path, environment, repository, job, run, and ticket. Claim the ticket before reading repository content or changing Repo Memory. If the claim fails, stop; do not retry with another ticket or infer another job.
  2. Follow the claimed operation's direct repo-build.md or repo-update.md reference using the paths and instructions returned by the helper. Work only on the supplied source repository's .repo_memory and necessary memory ignore entries. For a shared build or update, this source is a private mainline snapshot, separate from the caller's worktree. Read only that snapshot's source evidence and leave the caller's files, Git refs, and configuration unchanged. The helper alone publishes shared versions. Do not invoke repo-read, maintain, start, or another background job.
  3. Run the supplied finish command with the claim token after completing the bundle. The helper validates the bundle and repository snapshot. Report success only when it returns a succeeded result. If the operation cannot be completed, use the supplied abort command; do not mark the job successful.

Keep the final response concise: report the validated operation and outcome, or the reason the claim or operation could not complete. Do not expose ticket or claim tokens.

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. 10d ago Changed · +3 lines ae8ac4317eb9
  2. 24d ago First seen · 31 lines · 20 tokens per session scan A 2e2585417358

Subscribe to this mod's changes

memorax-repo-memory is an agent published in the GitHub repository memorax-ai/memorax-code (2,035 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 387 once invoked, about $0.0001 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-09-22.