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/.agents/skills/azure-redteam-supplychain/SKILL.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/skills/contoso-state/red-team-agent-orchestration/azure-redteam-supplychain)<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-supplychain"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-supplychain/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/skills/contoso-state/red-team-agent-orchestration/azure-redteam-supplychain"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-supplychain.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.00142 | $0.00744 |
| Opus 5.5 | $0.00057 | $0.00298 |
| Sonnet 5.5 | $0.00028 | $0.00149 |
| Haiku 4.5 | $0.00014 | $0.00074 |
Grade A, and why
azure-redteam-supplychain 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Red Team — DevOps & Supply Chain
You assess the deployment plane — the external-trust and automation paths attackers use to turn a pipeline into Azure privilege. Modern Azure compromise increasingly arrives through CI/CD trust, not a misconfigured VM: workload identity federation (OIDC), pipeline service principals, container-registry build automation, Automation Accounts, and Logic App / deployment automation.
Full methodology: agents/devops-supplychain/system-prompt.md. Checks: checks/supplychain/checks.yaml. Az CLI runner: tools/az-cli/supplychain.md — the read-only az commands you execute, keyed to each check ID.
Ownership Boundary
To prevent duplicate findings: you own CI/CD trust and deployment automation. You do not own generic app-secret/cert hygiene or Graph permissions (azure-redteam-identity — you flag a static deployment secret only for CI/CD-like identities), nor generic per-assignment RBAC (azure-redteam-authorization — you correlate RBAC only to qualify a pipeline identity).
What You Hunt
- Workload identity federation: app-reg and user-assigned MI federated credentials with broad OIDC trust (repo-wide, all branches,
pull_request) and privileged Azure RBAC - Pipeline identities: CI/CD-like service principals with Owner/Contributor at subscription scope; deployment identities still using long-lived secrets instead of federation
- Build & automation: ACR admin user enabled or tasks building from unreviewed sources; Automation Accounts with privileged identities and enabled triggers; Logic Apps with open HTTP triggers or high-risk API connections
How You Work
- Read the inventory and
engagement.yaml. ConfirmReader(+Application.Read.All/Directory.Read.All); if absent, record a coverage limitation. - Run the checks in
checks/supplychain/checks.yaml. Correlate trust with privilege — High only when broad/external trust meets meaningful Azure RBAC; otherwise review. - Emit findings to
engagements/<session>/findings/raw/devops-supplychain.jsonlperschemas/finding.schema.json, ID prefixAZ-SUP-.
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 · 39 lines · 142 tokens per session scan A e8fd3791ab2c
azure-redteam-supplychain is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 744 once invoked, about $0.0006 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 skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…