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-compute.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-compute)<a href="https://agentmods.dev/agents/contoso-state/red-team-agent-orchestration/redteam-compute"><img src="https://agentmods.dev/badge/agents/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/agents/contoso-state/red-team-agent-orchestration/redteam-compute"><img src="https://agentmods.dev/badge/agents/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.00090 | $0.00440 |
| Opus 5.5 | $0.00036 | $0.00176 |
| Sonnet 5.5 | $0.00018 | $0.00088 |
| Haiku 4.5 | $0.00009 | $0.00044 |
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 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 — 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): .claude/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.
- 1mo ago First seen · 33 lines · 90 tokens per session scan A a4f6cda5b635
redteam-compute is an agent published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 440 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
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.