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/postindustria-tech/agentic-toolkit/langgraph-dev-memory-store-and-knowledgenpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-memory-store-and-knowledgegit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWhat 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.00110 | $0.03045 |
| Opus 5 | $0.00055 | $0.01522 |
| Sonnet 5 | $0.00022 | $0.00609 |
| Haiku 4.5 | $0.00011 | $0.00304 |
Grade A, and why
Memory Store and Knowledge 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 3d 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Store and Knowledge Management
Build persistent, searchable memory systems for LangGraph agents using the Store interface.
Overview
LangGraph's Store interface enables agents to:
- Remember across conversations - Persist data beyond single threads
- Search semantically - Find relevant memories using natural language
- Isolate user data - Organize memories with namespaces
- Build knowledge - Accumulate facts and concepts over time
Unlike checkpointing (which saves workflow state within a thread), the Store provides cross-thread persistence for long-term knowledge retention.
Core Concepts
1. Store Interface
The Store is LangGraph's abstraction for persistent memory:
from langgraph.store.memory import InMemoryStore
# Basic store (key-value only)
store = InMemoryStore()
# Store with semantic search
from langchain.embeddings import init_embeddings
embeddings = init_embeddings("openai:text-embedding-3-small")
store = InMemoryStore(
index={
"embed": embeddings,
"dims": 1536,
}
)
When to use:
- User profiles and preferences
- Facts and knowledge bases
- Historical context across sessions
- Shared data between threads
2. Namespace Organization
Namespaces provide hierarchical isolation using tuples:
# Namespace structure: (category, user_id, [subcategory])
user_facts = ("memories", "user_123")
user_prefs = ("preferences", "user_123")
global_kb = ("knowledge_base",)
# Store data
store.put(user_facts, "fact_1", {"text": "User loves Python"})
store.put(user_prefs, "pref_1", {"theme": "dark"})
store.put(global_kb, "concept_1", {"topic": "LangGraph basics"})
Namespace patterns:
("memories", user_id)- Per-user facts("preferences", user_id)- User settings("knowledge_base",)- Global shared knowledge("conversations", user_id, thread_id)- Thread-specific episodic memory
3. Storing Data
Use store.put(namespace, key, value):
# Store with auto-generated key
store.put(
("memories", "user_123"),
"mem_001",
{
"text": "User mentioned they're learning DSPy",
"timestamp": "2026-01-13T10:00:00Z",
"context": "onboarding conversation"
}
)
# Store with indexing control
store.put(
("memories", "user_123"),
"mem_002",
{"text": "User completed tutorial"},
index=False # Don't embed this item
)
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .gitignore 64 B
- examples/01_basic_store.py 6.5 KB runs code
- examples/02_semantic_memory.py 11 KB runs code
- examples/03_vector_search_patterns.py 13 KB runs code
- examples/04_persistent_knowledge_agent.py 16 KB runs code
- references/production-memory-systems.md 16 KB
- references/vector-search-patterns.md 14 KB
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.
- 3d ago First seen · 500 lines · 110 tokens per session scan A 4fa78ac1dad2
Memory Store and Knowledge Management is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 3,045 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…