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-smsgit 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-sms)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-sms"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-sms/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-sms"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-sms.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.00184 | $0.01965 |
| Opus 5.5 | $0.00074 | $0.00786 |
| Sonnet 5.5 | $0.00037 | $0.00393 |
| Haiku 4.5 | $0.00018 | $0.00197 |
Grade A, and why
orchardcore-sms 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.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core SMS - Prompt Templates
Configure and Send SMS Messages
You are an Orchard Core expert. Generate code and configuration for SMS messaging including provider setup, programmatic sending, custom provider implementation, workflow integration, and SMS notifications.
Guidelines
- Enable
OrchardCore.Smsto access SMS settings and provider configuration. - The built-in providers are
Log(debugging only) andTwilio(production). - The
OrchardCore.Sms.Azurefeature adds Azure Communication Services as an additional provider. - After enabling the SMS feature, you must configure the default provider before sending messages.
- Use
ISmsServiceto send SMS messages programmatically. - Use
ISmsProviderto implement custom SMS providers. - Register simple providers with
AddSmsProvider<T>("TechnicalName"). - Register complex providers with settings using
AddSmsProviderOptionsConfiguration<T>(). - When both
SMSandWorkflowsfeatures are enabled, a "Send SMS" workflow task becomes available. - Enable
OrchardCore.Notifications.Smsfor user SMS notifications based on preferences. - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except for View Models.
Available SMS Providers
| Provider | Feature | Description |
|---|---|---|
Log |
OrchardCore.Sms |
Writes SMS messages to application logs. For debugging only — never use in production. |
Twilio |
OrchardCore.Sms |
Sends SMS via the Twilio service. Requires a Twilio account with SID, auth token, and phone number. |
Azure |
OrchardCore.Sms.Azure |
Tenant-specific Azure Communication Services SMS. Configure per tenant via admin settings. |
DefaultAzure |
OrchardCore.Sms.Azure |
Default Azure Communication Services configuration shared across all tenants. Configured via appsettings.json. |
Enabling SMS Features
{
"steps": [
{
"name": "Feature",
"enable": [
"OrchardCore.Sms"
],
"disable": []
}
]
}
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.
- 1mo ago First seen · 283 lines · 184 tokens per session scan A 6476711b14bc
orchardcore-sms is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 2d ago), licensed MIT. It adds 184 tokens to every session and 1,965 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.
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…
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).
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
contentful-cms
Contentful content types, GraphQL/REST queries, CLI migrations, assets and locales. Use when changing a Contentful content model, querying Contentful, or migrating its content.
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.
sfcc-hooks-registration
Register SFCC hooks via cartridge package.json and hooks.json. Use when adding hooks or troubleshooting hook registration.