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 crestapps-core-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/crestapps-core-elasticsearch)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-elasticsearch"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-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/crestapps-core-elasticsearch"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-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.00125 | $0.01335 |
| Opus 5.5 | $0.00050 | $0.00534 |
| Sonnet 5.5 | $0.00025 | $0.00267 |
| Haiku 4.5 | $0.00013 | $0.00134 |
Grade A, and why
crestapps-core-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 yesterday.
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps.Core Elasticsearch
Use Elasticsearch as the knowledge-base backend for AI documents, AI data sources and AI memory. For the data source model itself see crestapps-core-data-sources.
Registration
builder.Services.AddCrestAppsCore(crestApps => crestApps
.AddAISuite(ai => ai.AddOpenAI())
.AddIndexingServices(indexing => indexing
.AddYesSqlStores()
.AddElasticsearch(
builder.Configuration.GetSection("CrestApps:Elasticsearch"),
elasticsearch => elasticsearch
.AddAIDocuments()
.AddAIDataSources()
.AddAIMemory())));
The configuration section name is the host's choice. The sample hosts use CrestApps:Elasticsearch. AddElasticsearch(configure) without a section registers the services with no bound options.
| Call | Package | Adds |
|---|---|---|
AddCoreElasticsearchServices(section) |
CrestApps.Core.Elasticsearch |
ElasticsearchConnectionOptions, IElasticsearchClientFactory, a singleton ElasticsearchClient created by that factory, keyed IDataSourceContentManager, IDataSourceDocumentReader, IODataFilterTranslator, ISearchIndexManager, ISearchDocumentManager |
AddElasticsearchODataFilterTranslator() |
CrestApps.Core.Elasticsearch |
only the keyed IODataFilterTranslator, for hosts that bring their own clients and managers |
AddAIDocuments() / AddCoreElasticsearchAIDocumentSource() |
CrestApps.Core.AI.Elasticsearch |
AIDocuments index-profile source, profile handler, keyed IVectorSearchService |
AddAIDataSources() / AddCoreElasticsearchAIDataSource() |
CrestApps.Core.AI.Elasticsearch |
DataSource index-profile source, keyed ElasticsearchAIDataSourceSourceHandler, and AddCoreAIDataSourceRag() |
AddAIMemory() / AddCoreElasticsearchAIMemorySource() |
CrestApps.Core.AI.Elasticsearch |
AIMemory index-profile source, profile handler, keyed IMemoryVectorSearchService |
All keyed services use the provider name "Elasticsearch". Resolve them with [FromKeyedServices("Elasticsearch")], never unkeyed.
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.
- yesterday Changed · +26 lines · +102 tokens per session 2b40a0cde71e
- 1mo ago First seen · 60 lines · 23 tokens per session scan A a55f1262b3af
crestapps-core-elasticsearch is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 1,335 once invoked, about $0.0005 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
vector-backend-operations
Select and connect the right vector-store backend for the vector-mcp MCP server — chromadb, postgres/pgvector, qdrant, couchbase, or mongodb — and supply the correct dbtype/connection parameters that every collection and search call needs. Use when the agent must decide which engine to target, wire up…
vector-collection-management
Create, populate, list, and delete vector-store collections through the vector-mcp MCP server's vectorcollectionmanagement tool. Use when the agent must stand up a new RAG collection, ingest documents (from a directory, file paths/URLs, or raw text) into an existing collection, enumerate collections, or drop one …
vector-mcp-operations
Operate vector-mcp through its governed MCP and Arbora capabilities. Use for collection lifecycle, root-confined document ingestion, semantic or lexical retrieval, hybrid search, backend readiness, troubleshooting, and sanitized verification evidence.
pinecone
Managed vector DB for production RAG and search.
qdrant-search-quality-diagnosis
Diagnoses Qdrant search quality issues. Use when someone reports 'results are bad', 'wrong results', 'not relevant results', 'missing matches', 'recall is low', 'approximate search worse than exact', 'which embedding model', 'quality dropped after quantization', 'how to measure retrieval quality', 'build a golden…
microsoft-extensions-ai
Build provider-agnostic .NET AI integrations with Microsoft.Extensions.AI, IChatClient, embeddings, middleware, structured output, vector search, and evaluation. USE FOR: building or reviewing .NET code that uses Microsoft.Extensions.AI, Microsoft.Extensions.AI.Abstractions, IChatClient, IEmbeddingGenerator…