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 skills/shyftlabs/continuum/continuum-memorynpx skills add shyftlabs/continuum --skill continuum-memorygit clone --depth 1 https://github.com/shyftlabs/continuumWrote 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/shyftlabs/continuum/continuum-memory)<a href="https://agentmods.dev/skills/shyftlabs/continuum/continuum-memory"><img src="https://agentmods.dev/badge/skills/shyftlabs/continuum/continuum-memory.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.00107 | $0.01426 |
| Opus 5 | $0.00053 | $0.00713 |
| Sonnet 5 | $0.00021 | $0.00285 |
| Haiku 4.5 | $0.00011 | $0.00143 |
Grade A, and why
continuum-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 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.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuum Memory Skill
Authoritative sources: docs/memory.md and
docs/session.md.
Two layers
| Layer | Class | Backend | Purpose |
|---|---|---|---|
| Short-term | SessionClient |
Redis (port 6380) | Conversation history this session |
| Long-term | MemoryClient |
mem0 + Qdrant or Milvus | Facts extracted across sessions |
AgentRunner uses both automatically when user_id and session_id
are passed.
Vector store selection
Default is Milvus. Switch via env var:
VECTOR_STORE_PROVIDER=milvus # default — Milvus (port 19530)
VECTOR_STORE_PROVIDER=qdrant # Qdrant (port 6333)
Milvus config:
MILVUS_HOST=localhost
MILVUS_PORT=19530
MILVUS_TOKEN= # for Zilliz Cloud
MILVUS_COLLECTION=orchestrator_memories
Qdrant config:
QDRANT_HOST=localhost
QDRANT_PORT=6333
QDRANT_API_KEY= # for Qdrant Cloud
QDRANT_COLLECTION=orchestrator_memories
Quick agent setup
from continuum.agent import BaseAgent
from continuum.agent.config import AgentMemoryConfig
from continuum.agent.types import MemoryScope
agent = BaseAgent(
name="assistant",
instructions="...",
memory_config=AgentMemoryConfig(
search_memories=True,
store_memories=True,
search_scope=MemoryScope.USER, # ENUM, not the dataclass
store_scope=MemoryScope.USER,
search_limit=5,
),
)
resp = await runner.run(agent, "...", user_id="u1", session_id="s1")
Direct memory access
from continuum.memory import MemoryClient
client = MemoryClient() # uses env defaults
# add (fact extraction via LLM)
await client.add(
messages=[{"role": "user", "content": "I'm vegetarian"}],
user_id="u1",
)
# semantic search
result = await client.search("dietary preferences", user_id="u1", limit=5)
for entry in result.results:
print(entry.memory)
# CRUD
entry = await client.get(memory_id)
all_entries = await client.get_all(user_id="u1")
await client.update(memory_id, "Updated text")
await client.delete(memory_id)
await client.delete_all(user_id="u1") # wipe a user's memories
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 · 221 lines · 107 tokens per session scan A 594cabe7ba26
continuum-memory is a skill published in the GitHub repository shyftlabs/continuum (84 stars, last pushed today), licensed Apache-2.0. It adds 107 tokens to every session and 1,426 once invoked, about $0.0005 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-03.
Other skills, from other repositories
agenticx-memory-architect
Guide for setting up and using the AgenticX memory system including Mem0 integration, long-term memory, context management, and memory-enhanced agents. Use when the user wants to add memory to agents, persist conversation history, build memory-aware workflows, or integrate with Mem0 for long-term recall.
sql-helper
Генерация SQL по текстовому вопросу и DDL-схеме. Скрипт sqlhelper.py читает DDL-файл, строит in-memory схему в sqlite3, распознаёт слова вопроса по таблицам/колонкам и собирает SQL по шаблонам интентов (select, join, where, group, order, count, limit). Каждый кандидат проверяется через EXPLAIN, при --explain выводится…
preferences-memory
Use memory tools only when the user explicitly wants a stable fact or preference remembered beyond the current conversation.
session-persistence
Imports OpenClaw session transcripts into a local SQLite database with FTS5 full-text search — the agent never loses a message, even after context compaction or session rollover.
database-optimizer
Skill "database-optimizer" from aimerdoux/wavex-os, covering 🗄️ database optimizer, identity & memory, core mission, critical rules and communication style.
performance-oracle
Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…