red-team-agent-orchestration: Skill for Claude Code

.agents/skills/azure-redteam-web/SKILL.md

azure-redteam-web is a skill for Claude Code, Codex from Contoso-State/red-team-agent-orchestration. It costs 116 tokens per session (691 once invoked), scanned A, original, MIT.

An Azure web-edge and static-site security assessment skill. It reviews the services that sit in front of websites and APIs, such as Front Door, CDN, Application Gateway, API Management, and static website hosting.

In plain words
What is it for?
Use it to check WAF settings, HTTPS and TLS versions, custom-domain certificates, direct storage endpoints, protected routes, public APIs, subscription keys, and CORS.
Why use it?
It finds configuration gaps that can expose an application directly or leave it without adequate web filtering and encrypted connections. It focuses on the delivery edge rather than the application code itself.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is Contoso-State/red-team-agent-orchestration's own configuration. It tells Claude Code and Codex how to work on red-team-agent-orchestration itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything red-team-agent-orchestration configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Contoso-State/red-team-agent-orchestration/main/.agents/skills/azure-redteam-web/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Contoso-State/red-team-agent-orchestration

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 azure-redteam-web

README.md
[![agentmods](https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-web/github.svg)](https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-web)
Your own site
<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-web"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-web/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 azure-redteam-web

Your own site · 80×15
<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-web"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-web.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 691 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.
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.00116 $0.00691
Opus 5 $0.00058 $0.00345
Sonnet 5 $0.00023 $0.00138
Haiku 4.5 $0.00012 $0.00069

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

Security

Grade A, and why

azure-redteam-web 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.

.agents/skills/azure-redteam-web/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Azure Red Team — Web & Static Sites

You assess the web delivery edge — the public front door for content and APIs. Static Web Apps, Storage static websites, Front Door, CDN, Application Gateway, and API Management decide who can reach an application and whether a WAF and TLS stand in front of it.

Full methodology: agents/web-exposure/system-prompt.md. Checks: checks/web/checks.yaml. Az CLI runner: tools/az-cli/web.md — the read-only az commands you execute, keyed to each check ID.

What You Hunt

  • WAF posture: Front Door / Application Gateway with no WAF policy, or a WAF in Detection (log-only) mode instead of Prevention; default rule set disabled or outdated.
  • TLS / HTTPS: HTTPS-only not enforced; HTTP not redirected; minimum TLS < 1.2; missing or unbound custom-domain certificates.
  • Static endpoints: Storage account $web static-website endpoint exposed (and reachable directly, bypassing Front Door/WAF); Static Web Apps with no auth on protected routes.
  • API Management: gateway on public VNet/External with no IP restriction or product subscription requirement; APIs published without subscription keys or with open CORS.
  • Origin exposure: Front Door/CDN origin (App Service, storage, public IP) directly reachable, bypassing the WAF at the edge.

How You Work

  1. Read the inventory; filter to Microsoft.Cdn/profiles (Front Door/CDN), Microsoft.Network/applicationGateways, Microsoft.Network/frontdoorWebApplicationFirewallPolicies, Microsoft.Web/staticSites, Microsoft.ApiManagement/service, and Microsoft.Storage accounts with static website enabled.
  2. Run the checks in checks/web/checks.yaml.
  3. For a storage static website, assess the web-exposure angle and cross-reference the azure-redteam-data finding on the account; do not duplicate storage posture.
  4. Hand any unauthenticated internet-facing endpoint to azure-redteam-authorization for chaining.
  5. Emit findings to engagements/<session>/findings/raw/web-exposure.jsonl, ID prefix AZ-WEB-.

Read the full file on GitHub · 48 lines

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. 11d ago First seen · 48 lines · 116 tokens per session scan A fbf886e14a0d

Subscribe to this mod's changes

azure-redteam-web is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 7d ago), licensed MIT. It adds 116 tokens to every session and 691 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.