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/opencue/cuecards/agenticx-memory-architectnpx skills add opencue/cuecards --skill agenticx-memory-architectgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/agenticx-memory-architect)<a href="https://agentmods.dev/skills/opencue/cuecards/agenticx-memory-architect"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/agenticx-memory-architect.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.00067 | $0.01071 |
| Opus 5 | $0.00034 | $0.00535 |
| Sonnet 5 | $0.00013 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
agenticx-memory-architect 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 5d 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 agenticx-memory-architect — 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenticX Memory Architect
Guide for building agents with persistent memory capabilities.
Overview
AgenticX integrates with Mem0 for long-term memory, providing agents with the ability to remember past interactions, learn from experience, and maintain context across sessions.
Installation
pip install "agenticx[memory]"
# Includes: mem0, chromadb, qdrant-client, redis, milvus
Memory System Components
| Component | Purpose |
|---|---|
MemoryManager |
Core memory management interface |
Mem0Integration |
Bridge to Mem0's memory engine |
ContextMemory |
Short-term, session-scoped memory |
LongTermMemory |
Persistent, cross-session memory |
Basic Memory Usage
Initialize Memory
from agenticx.memory import MemoryManager
memory = MemoryManager(
provider="mem0",
config={
"llm": {"provider": "openai", "config": {"model": "gpt-4"}},
"vector_store": {"provider": "chroma"}
}
)
Store and Retrieve
# Add a memory
memory.add(
content="User prefers concise reports with bullet points",
user_id="user-123",
agent_id="analyst"
)
# Search memories
results = memory.search(
query="What format does the user prefer?",
user_id="user-123"
)
for r in results:
print(f"[{r.score:.2f}] {r.content}")
# Get all memories for a user
all_memories = memory.get_all(user_id="user-123")
Memory-Enhanced Agents
Attach Memory to an Agent
from agenticx import Agent, AgentExecutor
from agenticx.memory import MemoryManager
from agenticx.llms import OpenAIProvider
memory = MemoryManager(provider="mem0")
agent = Agent(
id="assistant",
name="Personal Assistant",
role="Assistant with memory",
goal="Help users while remembering their preferences",
organization_id="default"
)
executor = AgentExecutor(
agent=agent,
llm=OpenAIProvider(model="gpt-4"),
memory=memory
)
# First interaction — learns preference
result = executor.run(task_1)
# Later interaction — recalls preference
result = executor.run(task_2) # agent remembers context from task_1
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.
- 5d ago First seen · 175 lines · 67 tokens per session scan A a8c8985db9d3
agenticx-memory-architect is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,071 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agenticx-memory-architect, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
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.
chronicle-skysight
Use when recent Linux desktop activity memory would help answer a question or when the user asks to inspect or control Chronicle or Skysight.
context-engineering
项目级上下文工程框架:通过 PROJECT / REQUIREMENTS / ROADMAP / STATE 四层文档 为每个任务建立结构化上下文,控制 token 预算,防止上下文腐烂, 确保跨会话连续性。与 context-lifecycle 的 L0-L3 层互补。.
error-experience-library
错误经验库:自动捕获错误模式、根因和解决方案,支持查询和反馈更新。 当遇到 build error、runtime error 或需要查找历史错误解决方案时使用。.
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…