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 skills add binary16labs/prime-silo --skill memorygit clone --depth 1 https://github.com/binary16labs/prime-siloWrote 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/binary16labs/prime-silo/memory)<a href="https://agentmods.dev/skills/binary16labs/prime-silo/memory"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/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.
<a href="https://agentmods.dev/skills/binary16labs/prime-silo/memory"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/memory.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.00342 |
| Opus 5.5 | $0.00006 | $0.00137 |
| Sonnet 5.5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
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 1mo 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.
This is a copy
100% identical to Memory — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use prompt-include files as persistent memory.
paths
~/memory/behavior.system.include.md: stable behavior, user preferences, standing instructions, durable workflow rules~/memory/memories.transient.include.md: rolling notes worth keeping across conversations~/memory/*.transient.include.md: extra focused memory files when one topic deserves its own evolving note
rules
*.system.include.mdbecomes system-prompt instruction. Use it for slow-changing behavior.*.transient.include.mdbecomes transient context. Use it for notes, facts, project context, reminders, and other frequently updated memory.- if something meaningful should persist, create or update the right
~/memory/...include.mdfile instead of only acknowledging it in chat. - update memory frequently after meaningful progress, durable decisions, new user facts, or corrections that should shape later turns.
- when the user asks to change how you behave, edit
~/memory/behavior.system.include.md. - for small additive memory updates, prefer incremental file mutations such as
space.api.fileWrite({ path, content, operation: "append" })oroperation: "insert"over rereading and rewriting the whole memory file. Rewrite the full file only when you need cleanup, dedupe, or structural edits. - keep memory concise, specific, and current. Rewrite or delete stale lines instead of piling up duplicates.
- these files are plain markdown include bodies. Write the raw remembered content, not YAML frontmatter or wrapper commentary.
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.
- 1mo ago First seen · 27 lines · 15 tokens per session scan A b43e81d4d908
Memory is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 342 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Memory, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
memory-hygiene
Guidelines for writing and consolidating memories effectively in YodMCP.
notes
Skill "notes" from Pinvou/pinvou-agent, covering ima notes, operations, write rules, examples and response handling.
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
learn
Manually record an insight, correction, preference, or rule that the agent should remember for future tasks.
memory-kit
Create a workspace-local .cowork/ memory kit (rules, identity, long-term notes, daily logs, heartbeat templates).
memorywhale
Query and write durable debugging memory recorded by MemoryWhale. Use when debugging a failure that may have happened before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix worked and…