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 CrestApps/CrestApps.AgentSkills --skill orchardcore-ai-memory-elasticsearchgit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWrote 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/crestapps/crestapps.agentskills/orchardcore-ai-memory-elasticsearch)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-ai-memory-elasticsearch"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-ai-memory-elasticsearch/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/crestapps/crestapps.agentskills/orchardcore-ai-memory-elasticsearch"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-ai-memory-elasticsearch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00130 | $0.01519 |
| Opus 5 | $0.00065 | $0.00759 |
| Sonnet 5 | $0.00026 | $0.00304 |
| Haiku 4.5 | $0.00013 | $0.00152 |
Grade A, and why
orchardcore-ai-memory-elasticsearch 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 6d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core AI Memory Elasticsearch
Configure Elasticsearch memory indexing
You are an Orchard Core expert. Configure Elasticsearch as the persistent AI Memory vector backend while maintaining user isolation, stable provider mappings, and embedding compatibility.
Guidelines
- Enable the exact feature ID
CrestApps.OrchardCore.AI.Memory.Elasticsearch. - Its manifest depends on
CrestApps.OrchardCore.AI.MemoryandOrchardCore.Elasticsearch; the base memory feature is enabled by dependency. - Create AI Memory (Elasticsearch) from Search → Indexing, select an embedding deployment, and choose it in Settings → Artificial Intelligence → Memory.
- The provider is registered as keyed
IMemoryVectorSearchServiceusingElasticsearchConstants.ProviderName. - Vector similarity never replaces authorization. Every retrieval must remain filtered to the current authenticated
userId. - Install this package in the web or startup project and secure the Elasticsearch connection with production secret configuration.
- Store only durable non-sensitive preferences and facts; do not persist credentials, tokens, financial data, or private keys as AI memory.
Provider registrations
| Registration | Purpose |
|---|---|
AIMemoryElasticsearchIndexProfileHandler |
Defines memory mappings, vector dimensions, and default search fields. |
AIMemoryElasticsearchDocumentIndexHandler |
Maps persisted memory records to Elasticsearch documents. |
ElasticsearchMemoryVectorSearchService |
Runs user-filtered k-nearest-neighbor queries. |
AddElasticsearchIndexingSource |
Adds AI Memory (Elasticsearch) at Search → Indexing. |
Enable the backend
{
"steps": [
{
"name": "Feature",
"enable": [
"CrestApps.OrchardCore.AI",
"CrestApps.OrchardCore.AI.Memory.Elasticsearch",
"OrchardCore.Elasticsearch"
],
"disable": []
}
]
}
The core AI Memory feature comes from the provider dependency. Use the Azure AI Search provider instead when that is the selected index service; do not configure both as masters unless the application intentionally manages separate indexes and migration.
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.
- 6d ago First seen · 151 lines · 130 tokens per session scan A ce5243ffce83
orchardcore-ai-memory-elasticsearch is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 12d ago), licensed MIT. It adds 130 tokens to every session and 1,519 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-09-03.
Other skills, from other repositories
tanstack-ai-memory-redis
Use when wiring redis() from @tanstack/ai-memory/redis in production — covers client setup (ioredis or node-redis via fromNodeRedis), the storage model, client-side ranking limits, and troubleshooting.
iris-development
Iris is Redis's umbrella for AI-focused products. Use this skill when integrating with the Iris Redis Agent Memory (RAM) data plane on Redis Cloud — recording session events for an AI agent, creating or searching long-term memories, configuring a memory store, or tuning background memory promotion. Code examples use…
hermes-mnemosyne
Mnemosyne is Hermes' primary local-first memory engine — SQLite with vector + FTS5 hybrid search, 19+ tools, auto-consolidation, and a standalone CLI. It's a pip-installed plugin (not a built-in toolset) discovered via $HERMESHOME/plugins/mnemosyne/.
chroma-memory
Skill "chroma-memory" from iPythoning/b2b-sdr-agent-template, covering chroma-memory — per-turn conversation memory with chromadb, commands, usage, store a turn (normally auto-triggered by hook) and search history.
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"…
chromadb
Manage the ChromaDB vector database that stores the ecosystem's persistent memory. Use when user asks to check memory storage, backup memory, search stored entries, delete entries, or reset the vector database. Do NOT use for general question answering about past sessions (use the memory skill for that).