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-omnichannel-event-gridgit 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-omnichannel-event-grid)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-event-grid"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-event-grid/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-omnichannel-event-grid"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-event-grid.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.00139 | $0.01727 |
| Opus 5 | $0.00069 | $0.00864 |
| Sonnet 5 | $0.00028 | $0.00345 |
| Haiku 4.5 | $0.00014 | $0.00173 |
Grade A, and why
orchardcore-omnichannel-event-grid 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Omnichannel Azure Event Grid
Configure Event Grid Ingestion
You are an Orchard Core expert. Configure secure Azure Event Grid ingestion for the CrestApps Omnichannel pipeline, and implement handlers only for the events your application understands.
Guidelines
- Install
CrestApps.OrchardCore.Omnichannel.EventGridin the web/startup project. - Enable the base Omnichannel feature and the exact Event Grid feature ID
CrestApps.OrchardCore.Omnichannel.EventGrid. - The module exposes an anonymous
POSTendpoint atOmnichannel/webhook/AzureEventGrid; it disables antiforgery because Azure Event Grid cannot supply an Orchard antiforgery token. - Prefer a valid Microsoft Entra bearer token for Event Grid delivery. A configured
aeg-sas-keyrequest header is a supported shared-secret alternative. Do not expose an unauthenticated public webhook. - Configure all three AAD settings when using bearer authentication. A partial AAD configuration cannot validate a token and the request is rejected.
- Keep SAS keys and token configuration in user secrets, Key Vault, or environment-specific configuration. Never place a production secret in a recipe or source file.
- The endpoint accepts Event Grid event arrays and rejects request bodies larger than 1 MiB with HTTP 413.
- The module saves each normal event as an inbound
OmnichannelMessagein theOmnichannelYesSql collection, then invokes every registeredIOmnichannelEventHandler. - Event Grid payload normalization is deliberately generic. It checks common
data names such as
from,to,content,channel, andtimestamp; a channel-specific handler should interpret provider-specific data.
Feature and Package
| Item | Value |
|---|---|
| NuGet package | CrestApps.OrchardCore.Omnichannel.EventGrid |
| Base feature | CrestApps.OrchardCore.Omnichannel |
| Event Grid feature | CrestApps.OrchardCore.Omnichannel.EventGrid |
| Webhook route | POST /Omnichannel/webhook/AzureEventGrid |
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 · 191 lines · 139 tokens per session scan A 66fd6db15188
orchardcore-omnichannel-event-grid is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 13d ago), licensed MIT. It adds 139 tokens to every session and 1,727 once invoked, about $0.0007 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
aspire
Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting., DistributedApplication.CreateBuilder, apphost.mts…
azure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable Functions, bindings, or host configuration.…
manage-file-storage
Swap or remove the file storage provider (S3/MinIO).
alibaba-serverless-production-readiness
Review Function Compute 3.0 (FC3), SAE (Serverless App Engine), and EDAS for production readiness — cold start optimization, VPC binding, RAM role injection, ARMS distributed tracing, security group rules, concurrency limits, and SLA-readiness.
azure-app-service-production-readiness
Review Azure App Service and Web Apps for production readiness across plan tier fit, slots, networking, private ingress, identities, secrets, scaling, diagnostics, resilience, backup, rollback, and operator readiness. Use when a team wants a real go/no-go decision instead of shallow reassurance.
alibaba-event-driven-architecture-review
Review Alibaba Cloud EventBridge, MNS (Message Notification Service), RocketMQ, and MSE event-driven designs — dead-letter queues, message ordering, idempotency, retry storm prevention, schema registry, and consumer group lag monitoring.