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-messaginggit 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-messaging)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-messaging"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-messaging/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-messaging"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-messaging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.03121 |
| Opus 5.5 | $0.00081 | $0.01248 |
| Sonnet 5.5 | $0.00040 | $0.00624 |
| Haiku 4.5 | $0.00020 | $0.00312 |
Grade A, and why
orchardcore-omnichannel-messaging 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 today.
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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Omnichannel Messaging Workspace
Configure the Messaging Workspace
You are an Orchard Core expert. Set up the human messaging inbox, its SMS channel and permissions, and extend it with new channels through its contracts instead of changing the workspace.
Guidelines
- Install
CrestApps.OrchardCore.Omnichannel.MessagingandCrestApps.OrchardCore.Omnichannel.Messaging.Smsin the web/startup project. - The workspace carries no channel. Enable a channel feature; enabling SMS Messaging Channel enables the workspace and everything it needs.
- It does not need Contact Center Voice or the Omnichannel Management CRM screens; addresses come from the dependency-only Omnichannel Channel Endpoints feature.
- Where a number's texts go (queue or agent, hours, auto-replies) is set on its
Text messages inbound entry point, covered by
orchardcore-contact-center. - The workspace is the human counterpart to
orchardcore-omnichannel-sms; both run on the same numbers and an automated conversation hands off into it. - Keep provider secrets in Orchard Core SMS settings or configuration, never in
recipes or source. C# samples use
sealedclasses.
Features
| Feature | ID | Depends on |
|---|---|---|
| Omnichannel Messaging Workspace | CrestApps.OrchardCore.Omnichannel.Messaging |
CrestApps.OrchardCore.Omnichannel.ChannelEndpoints, CrestApps.OrchardCore.ContactCenter.AgentServices, CrestApps.OrchardCore.ContactCenter.EntryPoints, OrchardCore.SignalR |
| SMS Messaging Channel | CrestApps.OrchardCore.Omnichannel.Messaging.Sms |
the workspace, CrestApps.OrchardCore.ContactCenter.ProviderInbox, OrchardCore.Sms |
| Omnichannel Messaging Routed Distribution | CrestApps.OrchardCore.Omnichannel.Messaging.RoutedDistribution |
the workspace, CrestApps.OrchardCore.ContactCenter.Queues |
All are in the Contact Center category; the admin menu is Messaging (Inbox, Broadcasts, Templates).
{
"steps": [
{
"name": "Feature",
"enable": [
"CrestApps.OrchardCore.Omnichannel.Messaging.Sms",
"CrestApps.OrchardCore.Omnichannel.Messaging.RoutedDistribution"
],
"disable": []
}
]
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 266 lines · 202 tokens per session scan A bbbf5f4c7f64
orchardcore-omnichannel-messaging is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 202 tokens to every session and 3,121 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-10-22.
Other skills, from other repositories
fuzzy-selecting
Use when choosing interactively from search results, files, processes, or any command output with preview capabilities.
openclaw-management
This skill should be used when the user wants to interact with OpenClaw, delegate tasks to their AI assistant, or check gateway status. Activates for AI assistant delegation and orchestration.
org-search
Search and browse org-mode documents via the org MCP server. Use when the user wants to find content across org files, list their org documents, read file contents, or navigate headings and outlines. Triggers: "search my notes for...", "find org pages about...", "list my org files", "show outline of...", "read the…
issue_approve
Approve issue to transition to next workflow status.
architecture
Detailed architecture documentation including design decisions, processing patterns, and system internals. Use when discussing architecture, understanding why something was built a certain way, or planning significant changes.
any-mcp
Use when an agent needs to read, search, create, edit, organize, upload, or chat with Anytype through the bounded any-mcp server. Covers safe tool selection, exact identifier chaining, optional toolsets, common PKM workflows, and the narrow anyr fallbacks for chat subscriptions and rich chat blocks.