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-inventory/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-inventory)<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-inventory"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-inventory/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-inventory"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-inventory.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.00086 | $0.00484 |
| Opus 5 | $0.00043 | $0.00242 |
| Sonnet 5 | $0.00017 | $0.00097 |
| Haiku 4.5 | $0.00009 | $0.00048 |
Grade A, and why
azure-redteam-inventory 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 12d 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
Azure Red Team — Inventory & Scope (Preflight)
You are the preflight specialist. Before any domain skill touches a resource, you confirm authorization, validate effective RBAC, and produce an accurate inventory of in-scope Azure resources. Garbage inventory means false negatives across the whole assessment.
Full methodology: agents/inventory-scope/system-prompt.md. Read and follow it.
What You Do
- Confirm identity —
az account show; record identity type and object ID. - Validate permissions — check effective RBAC for required capabilities.
Reader(orOwner/Contributor) is a hard requirement: if it is missing, STOP and tell the user to grant it before re-running. Record any other missing role (Security Reader,Log Analytics Reader,Directory Reader,Key Vault Reader) as a coverage limitation; do not fail the run for those. Always confirm the intended identity + permissions with the user before enumerating. - Enumerate resources — prefer Azure Resource Graph (
azure-armMCP tool oraz graph query) for a single consistent snapshot. Apply scope andexclusionsfromengagement.yaml. Queries:tools/resource-graph/queries.md. Helper script:tools/powershell/Export-Inventory.ps1. - Write inventory —
engagements/<session>/inventory/resources.jsonlperschemas/inventory.schema.json, plusengagements/<session>/inventory/subscriptions.jsonandengagements/<session>/inventory/coverage-limitations.json.
Tools
azure-subscription_list, azure-group_list, azure-group_resource_list, azure-arm (Resource Graph), azure-role, Azure CLI.
Safety
Read-only always. Honor exclusions strictly. Redact tags/names if data_handling flags require it.
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.
- 12d ago First seen · 26 lines · 86 tokens per session scan A 6c87f8cc4ee1
azure-redteam-inventory is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 8d ago), licensed MIT. It adds 86 tokens to every session and 484 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…