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/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-telephony"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-telephony.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.00198 | $0.05033 |
| Opus 5.5 | $0.00079 | $0.02013 |
| Sonnet 5.5 | $0.00040 | $0.01007 |
| Haiku 4.5 | $0.00020 | $0.00503 |
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 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 — 281 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, a SignalR hub, call history, an internal extension registry, encrypted recording storage, and an optional floating soft phone. It does not provide SMS; use Orchard Core SMS (orchardcore-sms) or the Omnichannel skills for text messaging.
In this module, provider means the telephony backend adapter (Telnyx, Asterisk, or a custom PBX or carrier integration), not the phone company in the billing sense.
Guidelines
- Install
CrestApps.OrchardCore.Telephony(and any provider package) in the web/startup project. - Enable
CrestApps.OrchardCore.Telephonyfor the runtime services, the hub, call history, extensions, and the Settings → Communication → Telephony screen. There is no separate administration feature in 3.0. - The core feature depends on
OrchardCore.UsersandOrchardCore.SignalR(the Orchard Core framework SignalR module; seeorchardcore-signalr). - Enable
CrestApps.OrchardCore.Telephony.SoftPhoneonly when the floating widget or the front-end Soft Phone widget is needed. EnableCrestApps.OrchardCore.Telephony.SoftPhone.Extensionfor the standalone/softphonepage used by the browser extension and desktop app. - Enable a provider feature (
orchardcore-telephony-telnyx,orchardcore-telephony-asterisk, or your own) and select it as the default provider. - Call
ITelephonyServicefrom application code; never call a provider directly, because the service enforces capability, contract, and dial-destination checks. - Implement
ITelephonyProviderplus only the capability contracts the backend really supports, and advertise exactly thoseTelephonyCapabilities. - Read
TelephonyProviderOptionsthroughIOptionsMonitor<TelephonyProviderOptions>and callIOptionsUpdateNotifier.RequestUpdate<TelephonyProviderOptions>()after a provider's settings change. - Keep provider credentials and user tokens server-side; never send an API key or OAuth refresh token to browser code.
- Map hubs with
SignalRHubRoutes.GetHubPath<T>()and generate client URLs withHtml.SignalRHubUrl<T>();HubRouteManagerno longer exists. - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except for View Models.
What ships with it
3 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 · +76 lines · +75 tokens per session 5e5430b33657
- 1mo 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 9d ago), licensed MIT. It adds 198 tokens to every session and 5,033 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.