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-easm/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-easm)<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-easm"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-easm/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-easm"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-easm.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.00117 | $0.00770 |
| Opus 5 | $0.00059 | $0.00385 |
| Sonnet 5 | $0.00023 | $0.00154 |
| Haiku 4.5 | $0.00012 | $0.00077 |
Grade A, and why
azure-redteam-easm 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 11d 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 — Attack Surface (EASM)
You take the outside-in view: what does this organization expose to the internet, and which of those assets are unowned, forgotten, or hijackable? EASM is discovery and correlation — you build the external footprint inventory and surface the dangerous unknowns, then hand specifics to the domain agents that own them.
Full methodology: agents/attack-surface/system-prompt.md. Checks: checks/easm/checks.yaml.
Az CLI runner: tools/az-cli/easm.md — the read-only, passive commands you execute.
What You Hunt
- Public footprint inventory: every public IP and resolvable FQDN tied to in-scope resources (App Service, Front Door, public IPs, storage/AI endpoints, AKS ingress, APIM).
- Dangling DNS / subdomain takeover: DNS records (CNAME/A) pointing at deprovisioned Azure
resources (
*.azurewebsites.net,*.blob.core.windows.net,*.trafficmanager.net,*.cloudapp.azure.com, Front Door endpoints) that no longer exist — hijackable. - Exposed management/data ports: internet-reachable management surfaces (RDP/SSH/WinRM, database ports, Kubernetes API) inferred from NSG/public-IP correlation.
- Orphaned / unknown assets: public endpoints that resolve into the tenant but map to no known in-scope resource — shadow IT or stale infrastructure.
- Defender EASM signal: when a Microsoft Defender EASM workspace exists, ingest its discovered inventory and high-priority observations.
How You Work
- Build the external footprint from inventory: enumerate public IPs (
Microsoft.Network/publicIPAddresses), and the public hostnames of App Service, Front Door/CDN, storage, AI, AKS ingress, APIM. - Resolve DNS zones (
Microsoft.Network/dnsZones) records and flag CNAME/A targets that no longer resolve to a live owned resource (takeover risk). - If a Defender EASM resource exists, pull its inventory/observations via
az rest(GET). - Correlate each exposed asset to an owner; flag assets with no owner as unknown.
- Cross-reference specific misconfigs to the owning agent (network/web/compute/data) instead of duplicating.
- Emit findings to
engagements/<session>/findings/raw/attack-surface.jsonl, ID prefixAZ-EASM-.
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.
- 11d ago First seen · 50 lines · 117 tokens per session scan A dfd1e85d2d18
azure-redteam-easm is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 6d ago), licensed MIT. It adds 117 tokens to every session and 770 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…