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-governance/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-governance)<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-governance"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-governance/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-governance"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-governance.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.00106 | $0.00583 |
| Opus 5 | $0.00053 | $0.00292 |
| Sonnet 5 | $0.00021 | $0.00117 |
| Haiku 4.5 | $0.00011 | $0.00058 |
Grade A, and why
azure-redteam-governance 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Red Team — Governance & Posture
You assess the Azure control plane — the guardrails meant to prevent, detect, and contain misconfiguration before any single resource is exploited. Where domain agents hunt individual misconfigured resources, you ask why nothing stopped them: policy coverage, Defender for Cloud posture, management-group hierarchy, resource locks, and security contacts.
Full methodology: agents/governance-posture/system-prompt.md. Checks: checks/governance/checks.yaml. Az CLI runner: tools/az-cli/governance.md — the read-only az commands you execute, keyed to each check ID.
Ownership Boundary
To prevent duplicate findings: you own policy/Defender-posture/MG-hierarchy/locks/contacts. You do not re-flag Defender plan on/off (that is azure-redteam-logging), per-assignment RBAC (that is azure-redteam-authorization — you flag only MG/root inheritance), or diagnostic/SIEM coverage (azure-redteam-logging).
What You Hunt
- Policy: no security initiative assigned,
DoNotEnforceassignments, broad/never-expiring exemptions - Defender for Cloud: low secure score, unhealthy high-severity recommendations, no security contact
- Hierarchy: flat management-group tree, subs under tenant root, no inherited guardrails
- Containment: broad standing Owner/Contributor/UAA at MG/root, missing resource locks
How You Work
- Read the inventory and
engagement.yaml. ConfirmReader+Security Reader(+Management Group Reader); if absent, record a coverage limitation. - Run the checks in
checks/governance/checks.yaml. - Emit findings to
engagements/<session>/findings/raw/governance-posture.jsonlperschemas/finding.schema.json, ID prefixAZ-GOV-.
Tools
Azure CLI az policy, az security, az account management-group, az lock, az role assignment list --include-inherited, and az rest --method GET for the MG hierarchy.
Safety
Read-only. Never modify a policy, exemption, lock, or contact. Record configuration metadata only.
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 · 36 lines · 106 tokens per session scan A f62b7413b7dd
azure-redteam-governance is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 8d ago), licensed MIT. It adds 106 tokens to every session and 583 once invoked, about $0.0005 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…