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-telephonygit 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-telephony)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-telephony"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-telephony.svg" alt="Measured on agentmods" 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.00123 | $0.02344 |
| Opus 5 | $0.00062 | $0.01172 |
| Sonnet 5 | $0.00025 | $0.00469 |
| Haiku 4.5 | $0.00012 | $0.00234 |
Grade A, and why
orchardcore-telephony 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 5d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Telephony - Prompt Templates
Configure Provider-Agnostic Telephony
You are an Orchard Core expert. Generate accurate code, configuration, recipes, and administration guidance for the CrestApps Telephony module. It supplies a provider-neutral call-control layer and optional floating soft phone. It does not provide an SMS abstraction or SMS provider; use Orchard Core SMS or Omnichannel features for SMS.
Guidelines
- Install
CrestApps.OrchardCore.Telephonyin the web/startup project. - Enable
CrestApps.OrchardCore.Telephonyfor provider resolution, services, the hub, and call-history persistence. - Enable
CrestApps.OrchardCore.Telephony.Adminfor the Telephony settings screen and administration menu. - The core feature depends on
OrchardCore.UsersandCrestApps.OrchardCore.SignalR. - Enable
CrestApps.OrchardCore.Telephony.SoftPhoneonly when the floating widget is needed. - Select a default provider only after that provider feature is enabled and configured.
- Use
ITelephonyServicefrom application code; do not invoke a provider directly unless implementing framework infrastructure. - Implement
ITelephonyProviderin provider packages and declare only the capabilities actually supported. - Use
ITelephonyAuthenticationProvideronly when a provider requires per-user authentication. - Keep provider credentials and user tokens server-side; never send an API key or OAuth refresh token to browser code.
- Register a provider settings display driver in
TelephonyConstants.SettingsGroupIdso it appears on the Telephony settings screen. - Register hubs through
HubRouteManager, not a fixed route, to preserve tenant prefixes and site base URLs. - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except for View Models.
Feature Overview
| Feature | Feature ID | Purpose |
|---|---|---|
| Telephony | CrestApps.OrchardCore.Telephony |
Provider resolver, services, SignalR hub, OAuth routes, interaction history, and recording-store infrastructure |
| Telephony Administration | CrestApps.OrchardCore.Telephony.Admin |
Provider settings screen and administration menu |
| Telephony Soft Phone | CrestApps.OrchardCore.Telephony.SoftPhone |
Floating soft phone on the admin, front end, or both |
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.
- 5d ago First seen · 205 lines · 123 tokens per session scan A d3bca8474506
orchardcore-telephony is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 123 tokens to every session and 2,344 once invoked, about $0.0006 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
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
csharp-expert
Expert-level C# development with .NET 8+, ASP.NET Core, LINQ, async/await, and enterprise patterns. Use when the user mentions C#, .NET, ASP.NET, enterprise, or Microsoft platforms, or when the task involves Modern C#, Async/Await, LINQ, or ASP.NET Core.
sfcc-job-development
Guide for developing custom jobs in Salesforce B2C Commerce Job Framework. Use this when asked to create batch jobs, scheduled tasks, chunk-oriented processing, or task-oriented jobs.