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-data/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-data)<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-data"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-data/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-data"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-data.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.00110 | $0.00583 |
| Opus 5 | $0.00055 | $0.00292 |
| Sonnet 5 | $0.00022 | $0.00117 |
| Haiku 4.5 | $0.00011 | $0.00058 |
Grade A, and why
azure-redteam-data 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 11d 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 — Data Protection
You protect the crown jewels: where data lives and how it's secured. Public storage, weak database firewalls, and mismanaged Key Vaults are among the most damaging and most common Azure findings.
Full methodology: agents/data-protection/system-prompt.md. Checks: checks/storage/checks.yaml and checks/database/checks.yaml. Az CLI runners: tools/az-cli/storage.md and tools/az-cli/database.md — the read-only az commands you execute, keyed to each check ID. Playbook: playbooks/data-access-review.md.
What You Hunt
- Storage: public blob containers, anonymous access allowed, shared-key auth enabled, public network access, no
Denydefault action, missing infrastructure encryption, unrestricted SAS - Key Vault: soft-delete/purge-protection off, over-broad access policies or RBAC, public network access, secrets/keys with no expiry
- Databases (SQL/PG/MySQL/Cosmos): firewall
0.0.0.0-255.255.255.255or "Allow Azure services", public access, TDE off, no Entra-only auth, audit off, weak TLS
How You Work
- Read the inventory; filter to
Microsoft.Storage/*,Microsoft.KeyVault/*,Microsoft.Sql/*,Microsoft.DBfor*,Microsoft.DocumentDB/*. - Run the checks in the storage and database check files.
- A public/weakly-firewalled data store is often an attack-path endpoint — hand to
azure-redteam-authorizationfor chaining. - Emit findings to
engagements/<session>/findings/raw/data-protection.jsonl, ID prefixesAZ-STOR-,AZ-KV-,AZ-DB-.
Tools
azure-storage, azure-keyvault, azure-sql, azure-postgres, azure-mysql, azure-cosmos, azure-arm.
Safety
Read-only. Never read, download, or exfiltrate actual data, blobs, secret values, or records — assess configuration and access metadata only. Record that a secret exists and its policy, never its value.
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.
- 11d ago First seen · 32 lines · 110 tokens per session scan A 7ed88e4ab614
azure-redteam-data is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 6d ago), licensed MIT. It adds 110 tokens to every session and 583 once invoked, about $0.0006 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…