Borrowing it
Nothing to install: this file belongs to Contoso-State/red-team-agent-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Contoso-State/red-team-agent-orchestration/main/.agents/skills/azure-redteam-email/SKILL.mdgit clone --depth 1 https://github.com/Contoso-State/red-team-agent-orchestrationWrote 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/contoso-state/red-team-agent-orchestration/azure-redteam-email)<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-email"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-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/contoso-state/red-team-agent-orchestration/azure-redteam-email"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-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.00119 | $0.00733 |
| Opus 5 | $0.00060 | $0.00367 |
| Sonnet 5 | $0.00024 | $0.00147 |
| Haiku 4.5 | $0.00012 | $0.00073 |
Grade A, and why
azure-redteam-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 12d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Red Team — Email Security (Optional, Microsoft 365)
You assess whether the organization's email can be spoofed and whether inbound phishing is stopped. This is the Microsoft 365 / Exchange Online surface — adjacent to Azure but distinct — covering domain authentication and the EOP / Defender for Office 365 policy stack.
Scope note: Only run when
engagement.yamlincludes M365 / Exchange Online and the caller has Microsoft Graph / Exchange Online read access. This is not part of a baseline Azure assessment.
Full methodology: agents/email-security/system-prompt.md. Checks: checks/email/checks.yaml.
Runner: tools/az-cli/email.md — DNS lookups + Microsoft Graph (az rest GET) / Exchange Online
Get-* cmdlets.
What You Hunt
- SPF: missing record,
+all/?all(permissive), or no SPF at all — enables sender spoofing. - DMARC: missing record, policy
p=none(monitor-only), or no aggregate reporting — spoofed mail is not rejected/quarantined. - DKIM: signing not enabled for accepted domains; weak (1024-bit) keys.
- Anti-phishing (Defender for Office 365): no anti-phishing policy, spoof intelligence off, mailbox/impersonation protection disabled.
- Safe Links / Safe Attachments: disabled or not applied to all users.
- Connection filtering / EOP: permissive allow-lists, IP allow-lists bypassing spam filtering.
- Mail-flow / transport rules: rules that bypass spam filtering, auto-forward externally, or whitelist senders/domains broadly (data-exfil and phishing-bypass risk).
How You Work
- Enumerate accepted domains (Graph
GET /domains). - For each domain, resolve SPF (
TXT), DMARC (_dmarc.<domain>TXT), and DKIM selector records via DNS. - Read EOP / Defender for Office 365 policy posture via Microsoft Graph security/policy endpoints
(or Exchange Online PowerShell
Get-AntiPhishPolicy,Get-SafeLinksPolicy, etc. where available). - Review transport rules for external auto-forward and filter-bypass.
- Emit findings to
engagements/<session>/findings/raw/email-security.jsonl, ID prefixAZ-MAIL-.
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.
- 12d ago First seen · 50 lines · 119 tokens per session scan A da43abef62be
azure-redteam-email is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 7d ago), licensed MIT. It adds 119 tokens to every session and 733 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…