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 DemonDamon/AgenticX --skill agenticx-memory-architectgit clone --depth 1 https://github.com/DemonDamon/AgenticXWrote 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/demondamon/agenticx/agenticx-memory-architect)<a href="https://agentmods.dev/skills/demondamon/agenticx/agenticx-memory-architect"><img src="https://agentmods.dev/badge/skills/demondamon/agenticx/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/demondamon/agenticx/agenticx-memory-architect"><img src="https://agentmods.dev/badge/skills/demondamon/agenticx/agenticx-memory-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 15 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 171 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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 21d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agenticx-memory-architect — 100% identical, 2 lines differ
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.
- 21d ago Changed a5eb28e0c84b
- 1mo ago Changed a8f091009d09
- 1mo ago First seen · 175 lines · 67 tokens per session scan A b9d2761e6401
agenticx-memory-architect is a skill published in the GitHub repository DemonDamon/AgenticX (590 stars, last pushed today), licensed Apache-2.0. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
memory
Search past conversations in the agent's history log.
continuum-memory
Configure and use Continuum's two-tier memory system — mem0+Qdrant/Milvus for long-term facts, Redis for short-term sessions, with multi-tenant scopes (USER / AGENT / SHARED / RUN / CONVERSATION). Invoke when the user asks about "remember", "user preferences", "long-term memory", "vector search over memories"…
citedy-content-writer
From topic to published blog post in one conversation — generate SEO- and GEO-optimized articles with AI illustrations and voice-over in 55 languages, create social media adaptations for 9 platforms, set up automated content sessions, and manage product knowledge base. End-to-end blog autopilot. Powered by Citedy.
obsidian
A skill for working with an Obsidian vault, which is a folder of Markdown notes used as a personal knowledge base. It covers creating, extending, searching, and organizing notes, including links, tags, folders, and daily entries.
AgentDB Memory Patterns
Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.
V3 Memory Unification
Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).