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 skills/avids2/memorix/memorix-git-memorynpx skills add AVIDS2/memorix --skill memorix-git-memorygit clone --depth 1 https://github.com/AVIDS2/memorixWrote 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/skills/avids2/memorix/memorix-git-memory)<a href="https://agentmods.dev/skills/avids2/memorix/memorix-git-memory"><img src="https://agentmods.dev/badge/skills/avids2/memorix/memorix-git-memory.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.00292 |
| Opus 5 | $0.00015 | $0.00146 |
| Sonnet 5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
memorix-git-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 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.
What it actually says
Memorix Git Memory
Use Git Memory for repository evidence. Use reasoning memory for intent.
Tool Router
| Situation | Prefer | CLI fallback |
|---|---|---|
| Search what changed | memorix_search with a change-focused query |
memorix memory search --query "what changed <topic>" |
| Inspect a git-backed memory | memorix_detail |
memorix memory detail --id <id> |
| Ingest current commit manually | CLI | memorix ingest commit |
| Ingest a specific commit | CLI | memorix ingest commit --ref <ref> |
| Backfill recent history | CLI | memorix ingest log --count 20 |
| Install post-commit ingestion | CLI | memorix git-hook --force |
Retrieval Rules
- Prefer Git Memory for "what changed", "when did this ship", "which files were touched", and "which commit introduced this".
- Prefer reasoning memory for "why did we choose this", "what alternatives existed", and "what risk did we accept".
- Cross-link important decisions with
relatedCommitswhen storing reasoning. - Do not force-ingest noisy commits unless the skipped commit is genuinely important evidence.
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.
- 4d ago First seen · 27 lines · 31 tokens per session scan A 562473ac682c
memorix-git-memory is a skill published in the GitHub repository AVIDS2/memorix (717 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 292 once invoked, about $0.0002 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 skills, from other repositories
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
graph
Initialize or refresh the knowledge-graph snapshot for a repository. Ensures the codebase-memory-mcp engine is present (fetching it if needed), then builds draft/graph/ and reports engine, counts, hotspots, and cycles. Accepts an optional repo path.
deepnote
DeepNote knowledge base: persistent interlinked markdown wiki with ingest, query, lint, link graph and history.
aide-handoff
Record current pipeline state to .aide/session.aide — the project-wide pipeline-position log that lets the next session (yours or another agent's) resume from a known point. CREATE on first invocation per feature; UPDATE on every subsequent meaningful transition. This skill is the orchestration layer: it detects…
brain
Signpost to the brain — an external, team-shareable knowledge store that holds context too durable for the repo and too cross-project for any single codebase (domain research, coding playbook, project history, journal, environment, identity, references). When the current task needs knowledge that isn't in the working…
strategic-compact
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.