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.00187 | $0.02355 |
| Opus 5 | $0.00093 | $0.01177 |
| Sonnet 5 | $0.00037 | $0.00471 |
| Haiku 4.5 | $0.00019 | $0.00235 |
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 8d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Custom Indexing for Elasticsearch - Prompt Templates
Create a custom Elasticsearch index for arbitrary data
You are an Orchard Core expert. Generate code and configuration for indexing arbitrary records into Elasticsearch using Orchard Core index profiles, document handlers, and provider-specific mappings.
When to use this skill
Use this skill when the data source is not standard Orchard content-item indexing. Good examples:
- user-scoped AI memory records
- CRM or ERP records stored in a custom catalog
- generated AI summaries
- external records synchronized into a tenant document store
- any custom record set that needs full-text search, filtering, or vector search
Architecture to follow
Use the CrestApps AI Memory modules as the reference architecture:
CrestApps.OrchardCore.AI.Memorydefines the source record, master index settings, indexing service, and shared index-profile logic.CrestApps.OrchardCore.AI.Memory.Elasticsearchregisters the Elasticsearch indexing source and provider-specific handlers.CrestApps.OrchardCore.AI.Memory.AzureAIuses the same shared record/indexing pattern but with Azure AI Search mappings.
Master index pattern
For arbitrary data, create one logical master index profile type for that record family. Then:
- Store the source records in your own catalog/store.
- Configure a site setting that chooses the active index profile name.
- Build a provider-neutral index document model from each source record.
- Let provider-specific
IDocumentIndexHandlerimplementations map that neutral document into Elasticsearch fields. - Trigger indexing from the data lifecycle, not from one individual controller, tool, or UI action.
Key Orchard Core pieces
IIndexProfileStore- loads index profilesIndexProfileHandlerBase- reacts when an index profile is created, updated, or synchronizedIDocumentIndexHandler- maps a neutral record intoDocumentIndex- keyed
IDocumentIndexManager- writes provider-specific documents services.AddElasticsearchIndexingSource(type, options => ...)- registers a new index source in the admin UI
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.
- 8d 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 13d ago), licensed MIT. It adds 187 tokens to every session and 2,355 once invoked, about $0.0009 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
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 GraphOS 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.