orchardcore-sms-azure

orchardcore-sms-azure is a skill for Claude Code, Codex from CrestApps/CrestApps.AgentSkills. It costs 170 tokens per session (1,219 once invoked), scanned A, original, MIT.

A setup guide for adding Azure Communication Services SMS to Orchard Core, a .NET content-management platform. It explains how to configure the SMS provider and send messages through Orchard Core's common SMS service.

In plain words
What is it for?
Use it to enable Azure SMS, configure sending numbers and credentials, select the provider, and connect SMS sending to Orchard Core application code.
Why use it?
It removes the need to work out provider selection, tenant settings, phone-number formats, and secure connection-string configuration yourself.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to enable Azure SMS, configure sending numbers and credentials, select the provider, and connect SMS sending to Orchard Core application code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/crestapps/crestapps.agentskills/orchardcore-sms-azure
Install

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.

Any agent
npx skills add CrestApps/CrestApps.AgentSkills --skill orchardcore-sms-azure
Clone the repo
git clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for orchardcore-sms-azure

README.md
[![agentmods](https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-sms-azure/github.svg)](https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-sms-azure)
Your own site
<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-sms-azure"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-sms-azure/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.

agentmods 80×15 button for orchardcore-sms-azure

Your own site · 80×15
<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-sms-azure"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-sms-azure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 170 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,219 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00170 $0.01219
Opus 5.5 $0.00068 $0.00488
Sonnet 5.5 $0.00034 $0.00244
Haiku 4.5 $0.00017 $0.00122

Measured 1mo ago against content hash 7a0ecab496f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchardcore-sms-azure 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 1mo 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.

plugins/orchardcore/skills/orchardcore-sms-azure/SKILL.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orchard Core Azure Communication Services SMS

OrchardCore.Sms.Azure adds Azure Communication Services as a provider for the base OrchardCore.Sms module. It supplies tenant settings and a configuration-backed default provider. Use the base ISmsService from application code so another provider can be selected later without rewriting the sending service.

Guidelines

  • Enable OrchardCore.Sms before OrchardCore.Sms.Azure.
  • Select a configured and enabled SMS provider before attempting delivery.
  • Configure an ACS connection string and a phone number capable of sending SMS.
  • AzureSmsProvider is the tenant-configured provider; DefaultAzureSmsProvider reads host configuration.
  • Keep ACS connection strings in secure configuration, never in client-side code.
  • AzureSmsOptions.ConfigurationExists() requires both PhoneNumber and ConnectionString.
  • Use E.164 recipient phone numbers and validate them before sending.
  • Test with authorized destination numbers where the Azure account requires it.
  • All recipe JSON uses the root { "steps": [...] } format.

Enable Azure SMS

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "OrchardCore.Sms",
        "OrchardCore.Sms.Azure"
      ],
      "disable": []
    }
  ]
}

The Azure startup calls AddAzureSmsProvider(), registers AzureSmsOptionsConfiguration, provider options configuration, and the Azure settings display driver.

Configure Per Tenant

Navigate to Settings → Communication → SMS and configure Azure Communication Services. AzureSmsSettings contains:

Property Description
IsEnabled Enables the Azure provider for the tenant.
ConnectionString ACS connection string.
PhoneNumber ACS sending number in E.164 format.

After saving, select Azure in the SMS providers UI. The provider options configuration determines which tenant providers are available; merely enabling the feature does not select it.

Configure the Default Azure Provider

Read the full file on GitHub · 164 lines

Changes

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.

  1. 1mo ago First seen · 164 lines · 170 tokens per session scan A 7a0ecab496f1

Subscribe to this mod's changes

orchardcore-sms-azure is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 2d ago), licensed MIT. It adds 170 tokens to every session and 1,219 once invoked, about $0.0007 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-12.

Related

Other skills, from other repositories