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-compute)<a href="https://agentmods.dev/rules/contoso-state/red-team-agent-orchestration/redteam-compute"><img src="https://agentmods.dev/badge/rules/contoso-state/red-team-agent-orchestration/redteam-compute/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-compute"><img src="https://agentmods.dev/badge/rules/contoso-state/red-team-agent-orchestration/redteam-compute.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.00085 | $0.00420 |
| Opus 5 | $0.00043 | $0.00210 |
| Sonnet 5 | $0.00017 | $0.00084 |
| Haiku 4.5 | $0.00009 | $0.00042 |
Grade A, and why
redteam-compute 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 9d 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 — Compute Platform
Assess the machines and serverless apps that run code and hold managed identities — VMs/VMSS, App Service, and Functions. Containers and Kubernetes (AKS, ACR, Container Apps/Instances) belong to the Azure Container & Kubernetes Agent — defer those.
Methodology: agents/compute-platform/system-prompt.md. Checks: checks/compute/checks.yaml.
Skill (domain knowledge): .github/skills/azure-redteam-compute/SKILL.md.
Az CLI runner: tools/az-cli/compute.md.
Output
Run each check in checks/compute/checks.yaml via the runner. Flag any privileged managed identity
on internet-facing compute as a high-value pivot and note it for the authorization agent. Emit
findings to engagements/<session>/findings/raw/compute-platform.jsonl, ID prefix AZ-COMP-.
Boundary
If the inventory contains Microsoft.ContainerService, Microsoft.ContainerRegistry,
Microsoft.App, or Microsoft.ContainerInstance, leave them to the Azure Container & Kubernetes
Agent (checks/container/checks.yaml) — do not re-derive cluster/registry config.
Safety
Read-only. Never exec into VMs, never use run-command. Report a summary 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.
- 9d ago First seen · 32 lines · 85 tokens per session scan A ac1982e23cff
redteam-compute is a cursor rule published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 420 once invoked, about $0.0004 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 cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.