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-custom-indexing-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-custom-indexing-elasticsearch)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-custom-indexing-elasticsearch"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-custom-indexing-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-custom-indexing-elasticsearch"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-custom-indexing-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.00202 | $0.04327 |
| Opus 5.5 | $0.00081 | $0.01731 |
| Sonnet 5.5 | $0.00040 | $0.00865 |
| Haiku 4.5 | $0.00020 | $0.00433 |
Grade A, and why
orchardcore-custom-indexing-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 9d 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Custom Indexing for Elasticsearch
Index arbitrary records into Elasticsearch
You are an Orchard Core expert. Generate code that indexes custom records (not content items) into an Elasticsearch index profile, optionally with embeddings for vector search. Model it on CrestApps.OrchardCore.AI.Memory (records, settings, indexing service) and CrestApps.OrchardCore.AI.Memory.Elasticsearch (provider registration and mappings).
When to use it
- Records you store yourself: CRM or ERP rows, generated summaries, user-scoped facts, imported business data.
- Full-text, filtered, or vector search over them through Orchard Core's index profiles.
- For Orchard content items use the built-in content index instead (see
orchardcore-elasticsearch). For retrieval-augmented chat over an index you already have, an AI data source is usually enough (seeorchardcore-ai-data-sources).
Architecture
- A shared module owns the records, a provider-neutral index document, the master-index setting, and the indexing service.
- A provider module registers the index source, the index-profile handler that shapes the Elasticsearch mapping, and the
IDocumentIndexHandlerthat maps the neutral document. - Indexing runs from the record store's lifecycle, deferred to the end of the request, never from a single controller or tool.
- One index profile type per record family; a site setting picks the active profile by name.
Key pieces
| Piece | Namespace | Role |
|---|---|---|
AddElasticsearchIndexingSource(type, o => ...) |
OrchardCore.Elasticsearch |
Adds the index type to Search > Indexing |
IndexProfileHandlerBase |
OrchardCore.Indexing.Core.Handlers |
Shapes the profile on initialize, create, update, and reacts to SynchronizedAsync |
ElasticsearchIndexMetadata, ElasticsearchDefaultQueryMetadata |
OrchardCore.Elasticsearch.Core.Models, OrchardCore.Elasticsearch.Models |
Mapping and default query fields |
IDocumentIndexHandler, BuildDocumentIndexContext |
OrchardCore.Indexing |
Map a record into a DocumentIndex |
keyed IDocumentIndexManager |
OrchardCore.Indexing |
AddOrUpdateDocumentsAsync, DeleteDocumentsAsync per provider |
IIndexProfileStore |
OrchardCore.Indexing |
FindByNameAsync, GetByTypeAsync |
IndexProfileEmbeddingMetadataAccessor |
CrestApps.OrchardCore.AI.Core |
Reads the embedding deployment stored in DataSourceIndexProfileMetadata |
IAIDeploymentManager, IAIClientFactory |
CrestApps.Core.AI.Deployments, CrestApps.Core.AI.Clients |
Resolve the deployment and create the embedding generator |
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.
- 9d ago Changed · +220 lines · +15 tokens per session 058b67aaee64
- 1mo ago First seen · 282 lines · 187 tokens per session scan A 0e85d36dcfd3
orchardcore-custom-indexing-elasticsearch is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 9d ago), licensed MIT. It adds 202 tokens to every session and 4,327 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
solr-semantic-search
To build Solr phrase-tagging semantic search: concept tagging, taxonomy, graph paths.
solr-query
To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.
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.
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.