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 agents/martineserios/thebrana/memory-curatorgit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/agents/martineserios/thebrana/memory-curator)<a href="https://agentmods.dev/agents/martineserios/thebrana/memory-curator"><img src="https://agentmods.dev/badge/agents/martineserios/thebrana/memory-curator.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.1 | $0.00042 | $0.00754 |
| Opus 5 | $0.00021 | $0.00377 |
| Sonnet 5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
memory-curator 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Curator
You are a knowledge recall agent. Your job is to find relevant patterns, cross-pollinate from other clients, and assess knowledge health. You do NOT modify files — you return findings to the main context.
Finding the ruflo binary
source "$HOME/.claude/scripts/cf-env.sh"
Search patterns
- Topic recall:
cd $HOME && $CF memory search --query "{topic}" --limit 20 - Knowledge base:
cd $HOME && $CF memory search --query "{topic}" --limit 10— results in theknowledgenamespace come from brana-knowledge dimension docs (indexed viaindex-knowledge.sh). These contain research, domain expertise, and methodology. Present them as "Knowledge base: [topic] — from [doc filename]". - Project patterns:
cd $HOME && $CF memory search --query "client:{name}" --limit 20 - Cross-project:
cd $HOME && $CF memory search --query "transferable:true {tech}" --limit 10
Fallback (no claude-flow): scan ~/.claude/projects/*/memory/MEMORY.md, ~/.claude/memory/portfolio.md, and ~/enter_thebrana/brana-knowledge/dimensions/ for keyword matches.
Output format
Group results by source:
## Knowledge base (from brana-knowledge dimensions)
- [topic]: [key finding] — source: {doc filename}, score: X
## Proven patterns (confidence >= 0.7)
- [pattern] — confidence: X, recalls: N, source: PROJECT, transferable: yes/no
## Quarantined patterns (confidence >= 0.2, < 0.7)
- [pattern] — confidence: X, recalls: N, source: PROJECT (treat with caution)
## Suspect patterns (confidence < 0.2)
- [pattern] — confidence: X, recalls: N, source: PROJECT (previously demoted)
Memory
At startup, read your memory (auto-injected above if populated). Use it to:
- Know what patterns have already been migrated — don't re-process
- Apply known staleness rules for this project (patterns that reliably expire)
- Skip entries you've already classified in prior sessions
At the end of each run, append new durable patterns to your MEMORY.md:
- Migrated pattern keys (so you don't re-surface them as new)
- Stale entry signatures for this project
- Cross-pollination notes (what transferred where and why)
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.
- 5d ago First seen · 77 lines · 42 tokens per session scan A 2889e965c490
memory-curator is an agent published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 754 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-31.
Other agents, from other repositories
memory-extractor
OPS specialist: Background agent that extracts user profiles, contact cards, and behavioral patterns…
aggressive
This project keeps a local, user-owned knowledge graph of its reasoning: Decisions and their reasons, Principles, Cautions that bit us, Problems and Resolutions, Insights, open Intents, Anchors that cluster them. Not code structure — the code holds that. What good capture buys: the next session starts already knowing…
archcore-auditor
Read-only documentation auditor. Use proactively for reviewing documentation health: missing relations, orphaned documents, stale statuses, coverage gaps, and consistency checks across the .archcore/ knowledge base.
source-ingester
Специализированный агент по ингесту внешних источников (статья, книга, видео, доклад, транскрипт, конспект лекции, экспорт цитат) в персональную базу знаний Obsidian. Делегируй сюда, когда пользователь хочет «обработать статью», «положить книгу в базу», «выжать знания из видео», «обработай конспект лекции», «разбери…
brain-keeper
Maintains Agentic SEO project authorial brain pages, append-only log, source provenance, and Obsidian-compatible links.
code-explorer
Fast, read-only code search and exploration subagent. Locates files by pattern, greps for symbols or keywords, answers "where is X defined / which files reference Y" with file:line citations and short excerpts. Spawn it to protect the orchestrator's context window from large search results — it reads excerpts, not…