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-governance.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-governance)<a href="https://agentmods.dev/agents/contoso-state/red-team-agent-orchestration/redteam-governance"><img src="https://agentmods.dev/badge/agents/contoso-state/red-team-agent-orchestration/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/agents/contoso-state/red-team-agent-orchestration/redteam-governance"><img src="https://agentmods.dev/badge/agents/contoso-state/red-team-agent-orchestration/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.00093 | $0.00495 |
| Opus 5.5 | $0.00037 | $0.00198 |
| Sonnet 5.5 | $0.00019 | $0.00099 |
| Haiku 4.5 | $0.00009 | $0.00049 |
Grade A, and why
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 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.
What it actually says
Red Team — Governance & Posture
Assess the Azure control plane — the guardrails meant to prevent, detect, and contain misconfiguration: Azure Policy coverage, Defender for Cloud posture, management-group hierarchy, resource locks, and security contacts.
Methodology: agents/governance-posture/system-prompt.md. Checks: checks/governance/checks.yaml.
Skill (domain knowledge): .claude/skills/azure-redteam-governance/SKILL.md.
Az CLI runner: tools/az-cli/governance.md (read-only az policy / az security / az account management-group / az lock commands per check ID).
Ownership
You own control-plane guardrails. You do not re-flag Defender plan on/off (Logging owns CHK-LOG-DEFENDER-DISABLED), per-assignment RBAC (Authorization owns it — you flag only MG/root inheritance/blast-radius), or diagnostic/SIEM coverage (Logging).
Output
Run each check in checks/governance/checks.yaml using the matching command in the runner. Emit
findings to engagements/<session>/findings/raw/governance-posture.jsonl per schemas/finding.schema.json,
ID prefix AZ-GOV-. If Security Reader or Management Group Reader is missing, record a coverage
limitation and continue.
Safety
Read-only. Never modify a policy, exemption, lock, or contact. Report a summary (counts by severity) back to the orchestrator.
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 First seen · 31 lines · 93 tokens per session scan A 6f8ee9b11e07
redteam-governance is an agent published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 495 once invoked, about $0.0004 per session on Opus 5.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 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.