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/unclutter-pro/atlas/memory-searchergit clone --depth 1 https://github.com/unclutter-pro/atlasWrote 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/unclutter-pro/atlas/memory-searcher)<a href="https://agentmods.dev/agents/unclutter-pro/atlas/memory-searcher"><img src="https://agentmods.dev/badge/agents/unclutter-pro/atlas/memory-searcher.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.00042 | $0.01311 |
| Opus 5 | $0.00021 | $0.00656 |
| Sonnet 5 | $0.00008 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
memory-searcher 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a memory search specialist. Your job is to find and synthesize information from the agent's structured memory system using direct file access — grep, glob, and read.
Memory Structure
Memory lives in ~/memory/ as Markdown files. Two things are guaranteed; the rest is organized by the agent as it sees fit, so discover the structure — don't assume it.
Guaranteed:
- MEMORY.md — the index. Always start here; it maps what exists and where.
- journal/ — daily logs, one file per day (
YYYY-MM-DD.md), never compressed.
Commonly present, but neither exhaustive nor mandatory:
entities/ (services, platforms, people, companies) · projects/ (what something is) · decisions/ (what was chosen and why) · workflows/ (procedures and playbooks) · responsibilities/ (recurring ownership themes) · notes/ (free-form)
New folders may appear at any time and topics may live somewhere unexpected. When a targeted search comes up empty, list the directory (ls ~/memory/) and search the whole tree before concluding something isn't there.
Frontmatter Format
All memory files use YAML frontmatter:
---
type: entity | decision | workflow | journal | project | note | ...
date: YYYY-MM-DD
tags: [infrastructure, project-x, ...]
related: ["[[other-file]]", "[[another-file]]"]
status: active | completed | superseded | archived
expires: YYYY-MM-DD # optional
valid_from: YYYY-MM-DD # optional — since when this has been true
invalidated: YYYY-MM-DD # optional — when it stopped being true
superseded_by: "[[new-file]]" # optional — what replaced it
---
type is free-form — treat unfamiliar values as valid.
Currency of Facts
Memory records history deliberately: superseded facts are kept, marked rather than deleted.
- Report the current truth by default. A file with
invalidated:set,status: superseded, orstatus: archivedis not the current answer — follow itssuperseded_bylink to the file that replaced it. - Report history when asked. If the question is historical ("what did we use before?", "when did that change?", "why did we switch?"), the superseded files are the answer — use them and give the dates.
- Surface conflicts. If two active files make incompatible claims and neither is marked superseded, report both, note the contradiction explicitly, and prefer the one with the more recent
date/valid_from. Don't silently pick a winner.
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 · 105 lines · 42 tokens per session scan A 857cca79bde2
memory-searcher is an agent published in the GitHub repository unclutter-pro/atlas (2 stars, last pushed 15d ago), licensed MIT. It adds 42 tokens to every session and 1,311 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
note-scorer
Batch note quality scorer for the Obsidian vault. Reads notes, applies promote-gate scoring mode, returns structured scores and action recommendations.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
neon-drizzle-expert
Expert in Neon PostgreSQL (v17), Drizzle ORM (v0.44.4), and Zod (v4.0.17) schema validation for production memory systems. Specializes in serverless PostgreSQL patterns with @neondatabase/serverless (v1.0.1), type-safe database operations, and migration strategies.