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 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/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/opencue/cuecards/agenticx-memory-architect"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/agenticx-memory-architect.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.00067 | $0.01071 |
| Opus 5.5 | $0.00027 | $0.00428 |
| Sonnet 5.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 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 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.
- 1mo 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 (6 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.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
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
next
Produce a clean handoff to a fresh Claude Code window. Use when the current conversation is too long (>400K tokens, hallucinations, lost context, or the user wants to close the window). "/next" produces a handoff, "/next list" shows all pending, "/next remove X" deletes one.
session-compaction-and-restore
Use when reasoning about what survives compaction/context-loss/restart/seat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet…
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…
report
Writes the session final report to a file, then prints only the path and a one-line summary. Fires when the prompt contains "Report per memstack:report", and also when the prompt begins with a standing trigger configured through MEMSTACKREPORTONTASKPROMPTS or MEMSTACKREPORTTRIGGERS. Dormant otherwise.
save-learning
Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do X', 'from now on', 'never do Y', or gives any instruction they want persisted across sessions. Proactively suggest when the user states a preference, convention, or rule they clearly want followed in…