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 alexpizarro/azure-lean-stack-skills --skill adding-azure-communication-services-emailgit clone --depth 1 https://github.com/alexpizarro/azure-lean-stack-skillsWrote 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/alexpizarro/azure-lean-stack-skills/adding-azure-communication-services-email)<a href="https://agentmods.dev/skills/alexpizarro/azure-lean-stack-skills/adding-azure-communication-services-email"><img src="https://agentmods.dev/badge/skills/alexpizarro/azure-lean-stack-skills/adding-azure-communication-services-email/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/alexpizarro/azure-lean-stack-skills/adding-azure-communication-services-email"><img src="https://agentmods.dev/badge/skills/alexpizarro/azure-lean-stack-skills/adding-azure-communication-services-email.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.00113 | $0.01842 |
| Opus 5.5 | $0.00045 | $0.00737 |
| Sonnet 5.5 | $0.00023 | $0.00368 |
| Haiku 4.5 | $0.00011 | $0.00184 |
Grade A, and why
adding-azure-communication-services-email 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding Azure Communication Services Email
Transactional email via Azure Communication Services. Pay-as-you-go: $0.00025/email + $0.00012/MB, no free allowance — but 5,000 emails/month is about US$1.25, cheaper than any SendGrid tier for low-volume projects. Mind the rate limits: an Azure-managed domain is capped at 10 emails/hour (not raisable); a verified custom domain gets 100/hour and 30/minute, raisable by support ticket.
When to use ACS Email
| Need | Use |
|---|---|
| Account verification, password reset, transactional notifications | ACS Email (this skill) |
| Marketing campaigns, newsletters, A/B testing | A marketing-focused provider (Mailchimp, etc.) — ACS doesn't do that |
| High-volume bulk send (>100k/day) | SendGrid Pro or Mailgun (ACS gets expensive at scale) |
The three ACS quirks
1. location: 'global' (literal string, not a real Azure region)
resource emailService 'Microsoft.Communication/emailServices@2025-09-01' = {
name: emailServiceName
location: 'global' // ← NOT 'australiaeast', NOT location param
properties: { dataLocation: 'Australia' }
}
If you pass the project's location param (australiaeast), Azure rejects the deploy.
2. dataLocation uses plain English
The values for dataLocation are not Azure region IDs. They're region groupings:
dataLocation value |
Where data is stored |
|---|---|
'Australia' |
AU data centres |
'Europe' |
EU |
'United States' |
US |
'Asia Pacific' |
APAC excluding AU |
'Africa' |
Africa |
'Brazil' |
Brazil |
'Canada' |
Canada |
'France' |
France |
'Germany' |
Germany |
'India' |
India |
'Japan' |
Japan |
'Korea' |
Korea |
'Norway' |
Norway |
'Switzerland' |
Switzerland |
'UAE' |
UAE |
'United Kingdom' |
UK |
Use 'Australia' — not 'australiaeast', not 'au', not 'aus'.
3. Declare-order — no dependsOn on email service + domain
What ships with it
1 file 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.
- 1mo ago Changed 8cd1489ab1a5
- 1mo ago First seen · 193 lines · 113 tokens per session scan A 90f860f9d92e
adding-azure-communication-services-email is a skill published in the GitHub repository alexpizarro/azure-lean-stack-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 1,842 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
cloud-native-azure-functions
Use this skill when the user says 'azure functions', 'durable functions', 'orchestrator function', 'activity function', 'durable entities', 'event grid trigger', 'flex consumption', 'azure functions hosting plan', 'fan-out fan-in azure'. Designs Azure Functions apps and Durable Functions workflows with correct…
Application credential hygiene
Review application and service-principal ownership, credentials, permissions, and expiration risk without confusing registrations with enterprise applications.
Conditional Access review
Determine which policies apply to a user/application scenario and distinguish block, challenge, session restriction, report-only, and exclusions.
Entra user investigation
Build an evidence-backed identity dossier covering account state, roles, MFA, Conditional Access, and permitted activity.
Network diagnostics
Localize connectivity failures across DNS, routing, NSGs, firewalls, private endpoints, transport, TLS, and application response.
Virtual machine availability triage
Diagnose VM reachability and health by correlating resource state, platform health, recent changes, metrics, network controls, and in-VNet probes.