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 Kotrotsos/memento-core --skill memory-managementgit clone --depth 1 https://github.com/Kotrotsos/memento-coreWrote 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/kotrotsos/memento-core/memory-management)<a href="https://agentmods.dev/skills/kotrotsos/memento-core/memory-management"><img src="https://agentmods.dev/badge/skills/kotrotsos/memento-core/memory-management.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.00017 | $0.00553 |
| Opus 5 | $0.00009 | $0.00277 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
memory-management 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 7d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Management
You have access to the Memento MCP server for persistent memory. Use it proactively.
When to store
- After completing a significant task: what was built, key decisions, file paths
- When the user shares preferences or conventions
- After debugging: root cause and solution
- When discovering architecture patterns or project structure
- After research that produced useful findings
When to recall
- At the start of a session: search for context about the current project
- When the user references past work or decisions
- Before making architectural decisions: check for prior context
How to search effectively
- Start with
memory_list_namespacesto see what domains exist - Search with a focused query scoped to a specific namespace
- Use tags as pre-filters (they narrow before BM25 scoring)
- Only
memory_recallthe 1-3 most relevant results - Never recall all search results
How to write good memories
- Front-load the key fact (first 150 chars become the snippet)
- Be specific: "Use JSONL for storage" not "We decided on a storage format"
- One concept per memory
- Always include at least one tag
Namespace strategy
| Namespace | Use for |
|---|---|
global |
Cross-project knowledge |
projects/<name> |
Project-specific context |
people |
Person-related information |
decisions |
Architectural/design decisions |
procedures |
Repeatable workflows |
Tag vocabulary
| Tag | Use for |
|---|---|
architecture |
Design decisions, system structure |
preference |
User preferences, settings |
procedure |
How-to, workflows |
person |
People information |
project |
General project context |
temporary |
Short-lived, pair with TTL |
bug |
Known issues, workarounds |
learned |
Lessons, insights |
config |
Configuration, settings |
api |
API details, endpoints |
What NOT to store
- Conversation transcripts (store conclusions, not chats)
- Trivial changes (typo fixes, single-line edits)
- Temporary debugging output
- Information already in CLAUDE.md or project docs
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.
- 7d ago First seen · 79 lines · 17 tokens per session scan A e128c6f8d295
memory-management is a skill published in the GitHub repository Kotrotsos/memento-core (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 553 once invoked, about $0.0001 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 skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.