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-managementgit 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-management)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-management"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-management/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-management"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-omnichannel-management.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.00208 | $0.05096 |
| Opus 5.5 | $0.00083 | $0.02038 |
| Sonnet 5.5 | $0.00042 | $0.01019 |
| Haiku 4.5 | $0.00021 | $0.00510 |
Grade A, and why
orchardcore-omnichannel-management 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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Omnichannel Management (CRM)
Configure the Interaction Center
You are an Orchard Core expert. Build contact and activity work on the
Omnichannel Management module's existing model and extension points. Queues,
routing, agents and the dialer belong to the Contact Center
(orchardcore-contact-center); the human inbox belongs to
orchardcore-omnichannel-messaging.
Guidelines
- Install
CrestApps.OrchardCore.Omnichannel.Managementsin the web/startup project and enableCrestApps.OrchardCore.Omnichannel.Managements; it brings the headless and address features with it. - The module depends on
OrchardCore.Resources(it uses Orchard Core'sbootstrap-selectresource),OrchardCore.Flows,OrchardCore.ContentTypesand the CrestApps Users, ContentFields, PhoneNumbers and TimeZones features. - Read contact phone numbers and emails only through
IContactMethodsAccessor. - Configure a subject before loading activities for it, and enable a channel
processor (
orchardcore-omnichannel-sms,orchardcore-omnichannel-voice) before scheduling automated work. - Every admin list renders through Orchard Core's
AdminListshape (see the framework skillorchardcore-admin-lists). - C# samples use
sealedclasses and file-scoped namespaces.
Features
| Feature | ID | Notes |
|---|---|---|
| Omnichannel Activities | CrestApps.OrchardCore.Omnichannel.Activities |
Headless: catalogs, stores, managers, parts, indexes, migrations, permissions, recipe and deployment steps, api/omnichannel/subject-disposition-actions. |
| Omnichannel Channel Endpoints | CrestApps.OrchardCore.Omnichannel.ChannelEndpoints |
Dependency only. Interaction Center > Management > Omnichannel Addresses. Enabled by Management, Messaging Workspace, Contact Center Voice and Inbound Entry Points. |
| Omnichannel Management | CrestApps.OrchardCore.Omnichannel.Managements |
Admin screens, display drivers, menus, reports. |
| Omnichannel CRM | CrestApps.OrchardCore.Omnichannel.Crm |
Leads, accounts, opportunities. See references/crm.md. |
What ships with it
2 files 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.
- 9d ago Changed · +203 lines · +61 tokens per session 1eae62b431c5
- 1mo ago First seen · 221 lines · 147 tokens per session scan A ac8d6f5418ab
orchardcore-omnichannel-management is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 9d ago), licensed MIT. It adds 208 tokens to every session and 5,096 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
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
arrows-process-gaps-report
Arrows process gaps report: finds what's falling through the cracks in your pipeline, measured against your own sales process. Part 1 is what should be happening and isn't: promised follow-ups that never went out, deals quiet 14+ days with money at stake, missing next steps, single-threaded deals, no economic buyer…
edt-mcp-project-maintenance
Perform bounded EDT project maintenance through current EDT-MCP: diagnostics, revalidation, clean/resync, applications, database update, import/export, and Git when enabled.
p4-plan-search-queries
P4 Plan Find query syntax for advanced searching. Use when user needs to search, filter, or find items by status, assignee, priority, severity, dates, custom fields, or any combination.
metagit-aos
Compose ACL, task graph, scheduler, merge, and related coordination subsystems via metagit aos|coord status|doctor|next. Use when an operator or orchestrator needs one snapshot of coordination health or the next work envelope without launching models. Start with the day-1 quickstart for the canonical control loop.
agent-collaboration
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication.