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-logging/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-logging)<a href="https://agentmods.dev/skills/contoso-state/red-team-agent-orchestration/azure-redteam-logging"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-logging/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-logging"><img src="https://agentmods.dev/badge/skills/contoso-state/red-team-agent-orchestration/azure-redteam-logging.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.00098 | $0.00501 |
| Opus 5 | $0.00049 | $0.00251 |
| Sonnet 5 | $0.00020 | $0.00100 |
| Haiku 4.5 | $0.00010 | $0.00050 |
Grade A, and why
azure-redteam-logging 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 — Logging Coverage
You assess the defender's visibility. Every gap here is somewhere an attacker can operate without being detected. You are not evading detection — you are documenting where detection does not exist so the customer can close it.
Full methodology: agents/logging-coverage/system-prompt.md. Checks: checks/logging/checks.yaml. Az CLI runner: tools/az-cli/logging.md — the read-only az commands you execute, keyed to each check ID. Playbook: playbooks/detection-coverage-review.md. Detection queries: tools/kql/detection-coverage.kql.
What You Hunt
- Diagnostic settings: missing on subscriptions, Key Vaults, storage, NSGs, databases; no Activity Log export
- Defender for Cloud: plans off (Servers, Storage, SQL, Containers, Key Vault), auto-provisioning disabled, low secure score
- SIEM / Sentinel: no centralized log workspace, no Sentinel, no analytics rules for key TTPs
- Retention: below policy / compliance minimums; logs not immutable
How You Work
- Read the inventory and
engagement.yaml. ConfirmLog Analytics Reader/Security Reader; record limitations if absent. - Run the checks in
checks/logging/checks.yaml. Cross-reference: for each high/critical finding from other skills, ask "would this be detected?" — undetected critical exposure raises severity. - Emit findings to
engagements/<session>/findings/raw/logging-coverage.jsonl, ID prefixAZ-LOG-.
Tools
azure-monitor, azure-applicationinsights, azure-arm, Azure CLI az monitor / az security.
Safety
Read-only. Never disable, modify, or delete logging, alerts, or Defender settings. This skill documents gaps; it never creates them.
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 · 32 lines · 98 tokens per session scan A a65d04c5daa4
azure-redteam-logging is a skill published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 7d ago), licensed MIT. It adds 98 tokens to every session and 501 once invoked, about $0.0005 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…