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-azure-ai-searchgit 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-azure-ai-search)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-azure-ai-search"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-azure-ai-search/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-azure-ai-search"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-azure-ai-search.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.00193 | $0.03397 |
| Opus 5.5 | $0.00077 | $0.01359 |
| Sonnet 5.5 | $0.00039 | $0.00679 |
| Haiku 4.5 | $0.00019 | $0.00340 |
Grade A, and why
orchardcore-azure-ai-search 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 10d 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Azure AI Search - Prompt Templates
Configure Azure AI Search
You are an Orchard Core expert. Generate code and configuration for Azure AI Search integration in Orchard Core.
Guidelines
- Enable
OrchardCore.AzureAIto manage Azure AI Search indices (OrchardCore.Search.AzureAIis an obsolete feature id kept for compatibility). - Configure the Azure AI Search connection in
appsettings.jsonunderOrchardCore:Search:AzureAISearch(Orchard Core 4.0;OrchardCore_AzureAISearchis deprecated but still read) or through the admin UI at Settings > Search > Azure AI Search. - Read the effective connection settings with
IOptionsMonitor<AzureAISearchDefaultOptions>.CurrentValue. Admin settings changes refresh the monitor without a shell release, so a cachedIOptions<AzureAISearchDefaultOptions>.Valuegoes stale. - Use the
CreateOrUpdateIndexProfilerecipe step to create indexes (preferred over the obsoleteazureai-index-createstep). - Use the
ResetIndexrecipe step to restart indexing without deleting entries (preferred over the obsoleteazureai-index-resetstep). - Use the
RebuildIndexrecipe step to delete and recreate indexes (preferred over the obsoleteazureai-index-rebuildstep). - Supported authentication types:
ApiKey,Default,ManagedIdentity. - Use
IndexesPrefixto prevent naming conflicts when sharing an Azure AI Search instance across environments. - Enable
OrchardCore.Searchalongside Azure AI Search for frontend search functionality. - Azure AI Search uses a different field naming convention with double underscores (e.g.,
Content__ContentItem__FullText). - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier.
Enabling Azure AI Search Features
{
"steps": [
{
"name": "Feature",
"enable": [
"OrchardCore.Search",
"OrchardCore.AzureAI",
"OrchardCore.Indexing"
],
"disable": []
}
]
}
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.
- 10d ago Changed · +187 lines · +2 tokens per session 82ee5dbb9da9
- 1mo ago First seen · 244 lines · 191 tokens per session scan A 3430d0b9fc50
orchardcore-azure-ai-search is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 9d ago), licensed MIT. It adds 193 tokens to every session and 3,397 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
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
backend-development
Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability…
sast-idor
Detect Insecure Direct Object Reference (IDOR) vulnerabilities in a codebase using a three-phase approach: recon (find candidates), batched verify (check authorization in parallel subagents, 3 candidates each), and merge (consolidate batch results). Checks endpoints for missing ownership or authorization checks on…
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.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-service
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.