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 instructions/rebel0789/memory-recall/claude-mdgit clone --depth 1 https://github.com/rebel0789/Memory-RecallWrote 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/instructions/rebel0789/memory-recall/claude-md)<a href="https://agentmods.dev/instructions/rebel0789/memory-recall/claude-md"><img src="https://agentmods.dev/badge/instructions/rebel0789/memory-recall/claude-md.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.00057 | $0.00057 |
| Opus 5 | $0.00028 | $0.00028 |
| Sonnet 5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
Memory-Recall CLAUDE.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 today.
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
Claude-compatible repository entry
Read and follow AGENTS.md and ASSIGN_TO_AGENT.md. Run npm run status; only run npm run task -- <OAF-ID> when status names a next task. This file intentionally does not duplicate the canonical instructions.
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.
- today First seen · 4 lines · 57 tokens per session scan A 0c3783fef938
Memory-Recall CLAUDE.md is an instructions file published in the GitHub repository rebel0789/Memory-Recall (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session, about $0.0003 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-09-04.
Other instructions, from other repositories
sverklo CLAUDE.md
Instructions for sverklo/sverklo, covering sverklo development, using sverklo tools, project structure and build & test.
memex AGENTS.md
Instructions for iamtouchskyer/memex, covering memex — agent working instructions, what is this, before you touch anything, how the code is layered and files you'll actually need.
agentmako AGENTS.md
Instructions for drhalto/agentmako, covering mako mcp usage, operating model, default workflow, fast batches and freshness.
cortex-hub CLAUDE.md
Instructions for lktiep/cortex-hub, covering cortex hub — claude code instructions, quick start (mandatory), tech stack, code conventions and how to use cortex tools.
brain-os AGENTS.md
Instructions for brainOS-HQ/brain-os, covering agents.md, context, the hard rule, tool routing (in order) and mutation safety.
gnosys AGENTS.md
AGENTS.md instructions for proticom/gnosys, covering agents.md, what is gnosys, quick reference, architecture and key rules.