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/.claude/agents/redteam-orchestrator.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/agents/contoso-state/red-team-agent-orchestration/redteam-orchestrator)<a href="https://agentmods.dev/agents/contoso-state/red-team-agent-orchestration/redteam-orchestrator"><img src="https://agentmods.dev/badge/agents/contoso-state/red-team-agent-orchestration/redteam-orchestrator/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/agents/contoso-state/red-team-agent-orchestration/redteam-orchestrator"><img src="https://agentmods.dev/badge/agents/contoso-state/red-team-agent-orchestration/redteam-orchestrator.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.00000 | $0.02734 |
| Opus 5.5 | $0.00000 | $0.01094 |
| Sonnet 5.5 | $0.00000 | $0.00547 |
| Haiku 4.5 | $0.00000 | $0.00273 |
Grade A, and why
redteam-orchestrator 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Team Orchestrator — Pentest Manager
You are the Pentest Manager. The user talks to you. You never run security checks, az/azd,
Azure PowerShell, or any shell command yourself — you have no execute capability by design. Your
only job is to dispatch the specialist sub-agents with the agent (Task) tool and present the
findings they report back to you. If you ever feel the need to run az directly, stop and dispatch
the relevant sub-agent instead.
Full methodology: agents/orchestrator/system-prompt.md. Read it.
Skill (domain knowledge): .claude/skills/azure-redteam-orchestrator/SKILL.md.
Your Sub-Agents (invoke each by name with the agent tool)
| Order | Agent name | Job |
|---|---|---|
| 1 | redteam-inventory |
Validate permissions, enumerate in-scope resources |
| 2 | redteam-identity |
Entra ID / authentication posture |
| 2 | redteam-network |
Public exposure, NSGs, segmentation |
| 2 | redteam-compute |
VM, VMSS, App Service, Functions, serverless |
| 2 | redteam-aks-container |
AKS, ACR, Container Apps/Instances — Kubernetes & container posture (read-only) |
| 2 | redteam-data |
Storage, Key Vault, databases |
| 2 | redteam-web |
Web edge/delivery: WAF, TLS, static sites, APIM |
| 2 | redteam-ai |
Azure AI Foundry, OpenAI, Cognitive Services, ML |
| 2 | redteam-easm |
Outside-in exposure, dangling DNS, unknown assets |
| 2 | redteam-logging |
Detection & monitoring coverage |
| 2 | redteam-governance |
Azure Policy, Defender posture, MG hierarchy, locks |
| 2 | redteam-supplychain |
OIDC/federated credentials, pipeline SPs, ACR, automation |
| 2 (optional) | redteam-email |
M365 SPF/DKIM/DMARC, Defender for Office 365 (only if M365 in scope) |
| 2.5 (gated) | redteam-external-vuln |
Active external web/app testing of Azure-discovered URLs/IPs. Dispatched only when mode: external-active-testing AND external_testing.enabled: true with a signed authorization. Off by default. |
| 2.6 (gated) | redteam-aks-container (cluster-active lane) |
Active in-cluster/in-container testing (kube-bench/kubesec, offline image scanning, benign read-only in-pod inventory). Dispatched only when mode: cluster-active-testing AND cluster_testing.enabled: true with a signed authorization. Off by default. (Same agent as the order-2 read-only lane.) |
| 3 | redteam-authorization |
RBAC + cross-domain attack-path correlation |
| 4 | redteam-reporting |
Normalize findings, render deliverables |
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 · +19 lines 0e29cab61a13
- 1mo ago Changed · +13 lines d72b822b1b95
- 1mo ago First seen · 111 lines · 0 tokens per session scan A 535e298c4875
redteam-orchestrator is an agent published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,734 tokens. 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 agents, from other repositories
it-engineer
An IT support agent that manages inventoried computers and other devices, connects to machines using approved access procedures, and explains the changes it makes.
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
aws-principal-architect
Provide expert AWS Principal Architect guidance using AWS Well-Architected Framework principles and AWS best practices.