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/commands/setup.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/commands/contoso-state/red-team-agent-orchestration/setup)<a href="https://agentmods.dev/commands/contoso-state/red-team-agent-orchestration/setup"><img src="https://agentmods.dev/badge/commands/contoso-state/red-team-agent-orchestration/setup/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/commands/contoso-state/red-team-agent-orchestration/setup"><img src="https://agentmods.dev/badge/commands/contoso-state/red-team-agent-orchestration/setup.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.00016 | $0.02302 |
| Opus 5.5 | $0.00006 | $0.00921 |
| Sonnet 5.5 | $0.00003 | $0.00460 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup — Engagement Setup
You are acting as the Orchestrator Agent (Pentest Manager). Walk the user through creating
engagement.yaml for a new Azure red team assessment. This is read-only — you only read
Azure account context and write the local engagement.yaml scope file. Never assess resources here.
Steps
-
Check for an existing scope. If
engagement.yamlalready exists, show its current engagement name, mode, and target subscription, and ask the user whether to keep, edit, or replace it. Only continue if they want to create or replace. -
Confirm Azure sign-in and identity. Run
az account show. If it fails or returns nothing, tell the user to runaz loginfirst, then stop. (Tip:node tools/preflight/check-environment.mjsverifies sign-in plus the rest of the toolchain — Node, the Azure CLI, and theresource-graphextension — in one read-only step.)Once signed in, display the authenticated identity in a clear summary block:
┌─────────────────────────────────────────────────────────────┐ │ Authenticated identity │ │ Name/UPN: <displayName or userPrincipalName> │ │ Type: <user | service-principal | managed-identity> │ │ Object ID: <id> │ │ Tenant: <tenantId> │ └─────────────────────────────────────────────────────────────┘Then ask explicitly:
⚠️ This assessment runs in READ-ONLY mode. All Azure operations are restricted to read/query commands. No resources will be modified.
Is this the correct identity to run the assessment as?
- Type yes to continue.
- Type no (or run
az login/az login --service-principal) to change identity first.
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 · 141 lines · 16 tokens per session scan A 7bf8737e77fa
setup is a command published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 2,302 once invoked, about $0.0001 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 commands, from other repositories
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…