Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git 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/rules/contoso-state/red-team-agent-orchestration/redteam-governance)<a href="https://agentmods.dev/rules/contoso-state/red-team-agent-orchestration/redteam-governance"><img src="https://agentmods.dev/badge/rules/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/rules/contoso-state/red-team-agent-orchestration/redteam-governance"><img src="https://agentmods.dev/badge/rules/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.00087 | $0.00473 |
| Opus 5.5 | $0.00035 | $0.00189 |
| Sonnet 5.5 | $0.00017 | $0.00095 |
| Haiku 4.5 | $0.00009 | $0.00047 |
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): .github/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 · 30 lines · 87 tokens per session scan A 59845deea368
redteam-governance is a cursor rule published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 473 once invoked, about $0.0003 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 cursor rules, from other repositories
log-watch
Set up a scheduled agent that reads a small team's existing production logs, flags suspicious activity, and pages a human, without a SIEM or security staff. Use when the user mentions 'log watch,' 'watch my logs,' 'alert me if someone is attacking,' 'no SIEM,' 'poor man's SIEM,' 'agent reads CloudTrail,' 'cron job…
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.