Emulating Cloud Attacks with Stratus Red Team Agent Skill

Detonate granular AWS, Azure, GCP, and Kubernetes attack techniques to validate.

Context cost
6.5k tokensestimated from the bundle, loaded when it triggers
Bundle
5 files · 31.2 kB1 script among them — read before you run
Licence
Apache-2.0the author’s own terms
Last change
—v1.0
Servers it uses
Noneruns standalone

What it does

Detonate granular AWS, Azure, GCP, and Kubernetes attack techniques to validate

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

awsazuregcpkubernetessecuritytesting

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md11.0 kB · preview
--- name: emulating-cloud-attacks-with-stratus-red-team domain: cybersecurity subdomain: cloud-security tags: - stratus-red-team - adversary-emulation - cloud-security - detection-validation - purple-team - aws - mitre-attack - threat-detection version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - DE.CM-01 mitre_attack: - T1078 ---
24# Emulating Cloud Attacks with Stratus Red Team
25
26> **Legal Notice:** This skill is for authorized security testing and detection-validation purposes only. Stratus Red Team spins up and modifies real cloud infrastructure in the account whose credentials you supply. Only run it in accounts you own or are explicitly authorized to test. Always cleanup afterwards to avoid orphaned, billable, or insecure resources. Unauthorized use against systems you do not control is illegal.
27
28## Overview
29
30Stratus Red Team is an open-source "Atomic Red Team for the cloud," maintained by Datadog. It is a self-contained Go binary that programmatically *detonates* granular, well-documented offensive techniques against AWS, Azure, GCP, and Kubernetes, then lets you cleanly revert and remove everything it created. Unlike a full exploitation framework, Stratus is purpose-built for **detection engineering and purple teaming**: each technique maps to a MITRE ATT&CK tactic and ships with a precise description of the cloud API calls it generates, so a blue team can confirm whether their CloudTrail/GuardDuty/Sentinel/Falco detections actually fire.
31
32Every technique has a deterministic lifecycle. Stratus first provisions any prerequisite infrastructure with embedded Terraform (the **warmup** phase), then performs the malicious actions (**detonate**), optionally **revert**s the side effects so you can detonate again, and finally **cleanup**s the prerequisite infrastructure. Because the prerequisites and the attack are decoupled, you can iterate on a detection by detonating the same technique repeatedly without re-provisioning. The tool uses your standard cloud SDK credential chain (AWS profiles/env vars, az login, GCP ADC, kubeconfig), so it operates with exactly the permissions of the identity you authenticate as.
33
34This skill covers installing Stratus, listing and filtering the technique catalog, running the full warmup-detonate-revert-cleanup lifecycle, mapping detonations to the telemetry they produce, and wiring the results into a detection-validation workflow. Source: github.com/DataDog/stratus-red-team and stratus-red-team.cloud official documentation.
35
36## When to Use
37
38- Validating that a new or existing cloud detection rule (CloudTrail, GuardDuty, Microsoft Sentinel, GCP SCC, Falco) actually triggers on real attacker activity
39- Building a repeatable purple-team exercise for cloud TTPs without writing bespoke attack scripts
40- Generating realistic, MITRE-mapped telemetry to test SIEM ingestion and alert routing
41- Measuring detection coverage of a cloud environment against a known catalog of techniques
42- Onboarding analysts with safe, reversible hands-on cloud attack simulations
43
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,417 words
Files5
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈120
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
6,380
on trigger
The instruction body and 4 supporting files, read only when the skill fires.
3.3%
of a 200k window
Ten skills this size would take about 33% of the window before you open a file.
050k100k150k200k context window

6.5k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

5 files, 31.2 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to.

  • SKILL.md11.0 kB
  • LICENSE11.3 kB
  • references/api-reference.md2.4 kB
  • references/standards.md1.3 kB
  • scripts/agent.py5.2 kB
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the bundle is 5 files you can review in full before installing. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Emulating Cloud Attacks with Stratus Red Team · 6.5k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/emulating-cloud-attacks-with-stratus-red-team/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/emulating-cloud-attacks-with-stratus-red-team" ] && { [ ! -e .claude/skills/emulating-cloud-attacks-with-stratus-red-team ] || { mv .claude/skills/emulating-cloud-attacks-with-stratus-red-team "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/emulating-cloud-attacks-with-stratus-red-team" .claude/skills/ && echo "Installed .claude/skills/emulating-cloud-attacks-with-stratus-red-team"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add sueytame/emulating-cloud-attacks-with-stratus-red-team

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/emulating-cloud-attacks-with-stratus-red-team/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/emulating-cloud-attacks-with-stratus-red-team/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/emulating-cloud-attacks-with-stratus-red-team" ] && { [ ! -e ~/.claude/skills/emulating-cloud-attacks-with-stratus-red-team ] || { mv ~/.claude/skills/emulating-cloud-attacks-with-stratus-red-team "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/emulating-cloud-attacks-with-stratus-red-team" ~/.claude/skills/ && echo "Installed ~/.claude/skills/emulating-cloud-attacks-with-stratus-red-team" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/emulating-cloud-attacks-with-stratus-red-team/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version1.0
Publishedno release date on file
PriceFree
Referencesueytame/emulating-cloud-attacks-with-stratus-red-team

Versions

v1.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v1.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill