orchardcore-email-smtp

orchardcore-email-smtp is a skill for Claude Code, Codex from CrestApps/CrestApps.AgentSkills. It costs 104 tokens per session (646 once invoked), scanned A, original, MIT.

A setup guide for sending Orchard Core email through SMTP, the standard protocol used by many mail servers and email services. It covers network settings, encryption, credentials, and provider selection.

In plain words
What is it for?
Use it to configure SMTP delivery, pickup directories, recipes, default settings, and the email provider used by applications.
Why use it?
It removes the guesswork from connecting Orchard Core to an SMTP server and helps move older SMTP-specific code to the general email service.

Skill for Claude CodeCodex

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

Good fit Use it to configure SMTP delivery, pickup directories, recipes, default settings, and the email provider used by applications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/crestapps/crestapps.agentskills/orchardcore-email-smtp
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-email-smtp
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-email-smtp

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-email-smtp"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-email-smtp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 646 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00104 $0.00646
Opus 5 $0.00052 $0.00323
Sonnet 5 $0.00021 $0.00129
Haiku 4.5 $0.00010 $0.00065

Measured 5d ago against content hash 7d05795036e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

orchardcore-email-smtp 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.

plugins/orchardcore/skills/orchardcore-email-smtp/SKILL.md · 91 lines

What it actually says

Orchard Core SMTP Email Provider

OrchardCore.Email.Smtp supplies the tenant SMTP provider and the configuration-backed DefaultSMTP provider. Application code uses IEmailService, not an SMTP-specific service.

Enable the module and configure Settings → Communication → Email. Select the enabled SMTP provider as the email default when more than one provider is enabled. The last valid enabled provider is selected automatically.

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "OrchardCore.Email",
        "OrchardCore.Email.Smtp"
      ]
    },
    {
      "name": "Settings",
      "SmtpSettings": {
        "IsEnabled": true,
        "DefaultSender": "[email protected]",
        "Host": "smtp.example.com",
        "Port": 587,
        "AutoSelectEncryption": false,
        "EncryptionMethod": "STARTTLS",
        "RequireCredentials": true,
        "UserName": "smtp-user",
        "Password": "supply-from-a-secret-store",
        "DeliveryMethod": "Network"
      },
      "EmailSettings": {
        "DefaultProviderName": "SMTP"
      }
    }
  ]
}

For centrally managed defaults, configure DefaultSmtpOptions through OrchardCore_Email_Smtp; its technical name is DefaultSMTP. Store passwords outside source control.

For pickup delivery set DeliveryMethod to SpecifiedPickupDirectory and use a valid relative PickupDirectoryLocation. The configuration-backed provider also supports PickupDirectoryLocationBase.

using OrchardCore.Email;
using OrchardCore.Infrastructure;

namespace MyModule;

public sealed class ReceiptService
{
    private readonly IEmailService _emailService;

    public ReceiptService(IEmailService emailService)
    {
        _emailService = emailService;
    }

    public Task<Result> SendAsync(string recipient)
    {
        return _emailService.SendAsync(new MailMessage
        {
            To = recipient,
            Subject = "Receipt",
            HtmlBody = "<p>Your receipt is ready.</p>",
            TextBody = "Your receipt is ready.",
        });
    }
}

ISmtpService, SmtpResult, MailKitSmtpService, Body, and IsHtmlBody are obsolete names or members. Test a selected enabled provider at Tools → Testing → Email Test.

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. 5d ago First seen · 91 lines · 104 tokens per session scan A 7d05795036e6

Subscribe to this mod's changes

orchardcore-email-smtp is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 11d ago), licensed MIT. It adds 104 tokens to every session and 646 once invoked, about $0.0005 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.

Related

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…

czlonkowski/n8n-mcp · 221 tokens

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…

managedcode/dotnet-skills · 122 tokens

tech-specs

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

griddynamics/rosetta · 23 tokens

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

SebastienDegodez/copilot-instructions · 50 tokens

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.

personamanagmentlayer/pcl · 70 tokens

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.

taurgis/sfcc-dev-mcp · 40 tokens