Agent skill

Atmos AWS Security

AWS security finding analysis: analyze findings, map to Atmos components/stacks, generate structured remediation with exact Terraform changes and deploy commands

Apache-2.0Auto-check passedDevOps & Cloud

Install Atmos AWS Security

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-aws-security -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-aws-security --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skills/skills/atmos-aws-security .claude/skills/atmos-aws-security && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "atmos-aws-security" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-aws-security into .claude/skills/atmos-aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-aws-security", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-aws-security

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-aws-security -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-aws-security --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agent-skills/skills/atmos-aws-security .agents/skills/atmos-aws-security && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "atmos-aws-security" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-aws-security into .agents/skills/atmos-aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-aws-security", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-aws-security -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-aws-security --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agent-skills/skills/atmos-aws-security .cursor/skills/atmos-aws-security && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "atmos-aws-security" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-aws-security into .cursor/skills/atmos-aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-aws-security", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/cloudposse/atmos.git --path agent-skills/skills/atmos-aws-security

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-aws-security -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-aws-security --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agent-skills/skills/atmos-aws-security .gemini/skills/atmos-aws-security && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "atmos-aws-security" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-aws-security into .gemini/skills/atmos-aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-aws-security", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-aws-security

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-aws-security -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .github/skills && cp -r skills-src/agent-skills/skills/atmos-aws-security .github/skills/atmos-aws-security && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "atmos-aws-security" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-aws-security into .github/skills/atmos-aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-aws-security", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cloudposse/atmos --skill atmos-aws-security -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install cloudposse/atmos atmos-aws-security --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agent-skills/skills/atmos-aws-security .opencode/skills/atmos-aws-security && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "atmos-aws-security" agent skill from https://github.com/cloudposse/atmos/tree/main/agent-skills/skills/atmos-aws-security into .opencode/skills/atmos-aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atmos-aws-security", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: atmos-aws-security
GitHub stars: 1.4k
Token cost: ~867 tokens
SKILL.md length: 375 words
Files: 1
Skills in repo: 70
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

AWS security finding analysis: analyze findings, map to Atmos components/stacks, generate structured remediation with exact Terraform changes and deploy commands

Works in 3 steps: First step → Second step → Third step
Tasks that involve Cloud security
SKILL.md covers Output Format, Context You Receive and Analysis Guidelines
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Atmos AWS Security is an agent skill from cloudposse/atmos. AWS security finding analysis: analyze findings, map to Atmos components/stacks, generate structured remediation with exact Terraform changes and deploy commands

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Cloud security and Infrastructure as code. It works with Terraform. The repository describes itself as: Atmos is the open-source runtime for infrastructure — it builds, authenticates, and ships Terraform, OpenTofu, Packer, Ansible, Kubernetes, Helm, and containers the same way on… The licence is Apache-2.0.

When your agent uses it

Tasks that involve Cloud security
Tasks that involve Infrastructure as code

Example prompts

“/atmos-aws-security”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

First step
Second step
Third step

What it can do on your machine

Read from SKILL.md and the folder at commit 36726ae. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are hcl, yaml and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Atmos AWS Security loads about 867 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 375 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~45
When it runs · the whole SKILL.md, loaded when a task matches: ~867

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cloudposse/atmos at commit 36726ae, republished under its Apache-2.0 licence (© cloudposse). 375 words, ~867 tokens.

Download SKILL.mdSave it as .claude/skills/atmos-aws-security/SKILL.md (or your agent's skills folder).

name: atmos-aws-security
description: AWS security finding analysis: analyze findings, map to Atmos components/stacks, generate structured remediation with exact Terraform changes and deploy commands
metadata.copyright: Copyright Cloud Posse, LLC 2026
metadata.version: 1.0.0
metadata.category: security

Atmos AWS Security Finding Analysis

You are analyzing AWS security findings that have been mapped to Atmos infrastructure components. Your job is to provide consistent, structured remediation guidance that follows an exact format.

Output Format

You MUST return your analysis using these exact section headers. Every section is required. The output is parsed programmatically — do not deviate from the format.

Root Cause

Explain WHY this finding exists in the infrastructure. Reference the specific Terraform resource or stack configuration that caused it. Be specific — name the resource type, the missing attribute, or the misconfigured setting.

Steps

Return an ordered list of remediation steps. Each step should be a concrete action. Use numbered list format:

First step
Second step
Third step

Code Changes

Show the specific Terraform/HCL changes needed. Use the component source code provided in the context. Format as a diff or before/after:

hcl

# Before
resource "aws_s3_bucket" "this" {
  bucket = var.bucket_name
}

# After
resource "aws_s3_bucket" "this" {
  bucket = var.bucket_name
}

resource "aws_s3_bucket_versioning" "this" {
  bucket = aws_s3_bucket.this.id
  versioning_configuration {
    status = "Enabled"
  }
}

Stack Changes

Show the specific stack YAML changes needed. Reference the exact vars key to add or modify:

yaml

# stacks/deploy/prod/us-east-1.yaml
components:
  terraform:
    s3-bucket:
      vars:
        versioning_enabled: true

Deploy

Provide the exact atmos terraform apply command to deploy the fix:

bash

atmos terraform apply <component> -s <stack>

Risk

Rate the risk of applying this remediation: low, medium, or high.

low — Read-only change, no service disruption
medium — Config change that may cause brief disruption
high — Destructive change (resource replacement, data loss risk)

References

List relevant AWS documentation URLs, CIS benchmark controls, or compliance framework references.

Show full SKILL.md (153 more words)Show less

Context You Receive

For each finding, you will receive:

Finding details — ID, title, description, severity, source service, resource ARN, region
Component mapping — Atmos stack name, component name, component path, confidence level
Component source — The main.tf content from the Terraform component (if available)
Stack config — The resolved stack configuration for the component (if available)

Analysis Guidelines

Always reference the specific Terraform resource that needs to change.
If the component source is provided, reference actual variable names from the code.
If the component source is NOT provided, use common Cloud Posse component conventions.
The deploy command MUST use the exact stack and component names from the mapping.
For unmapped findings (no Atmos component identified), still provide general remediation but note that the component could not be automatically identified.
Prefer variable changes in stack YAML over direct Terraform code changes when possible (Atmos convention: configuration lives in stacks, not in component code).

Files

Just SKILL.md in agent-skills/skills/atmos-aws-security of cloudposse/atmos.

Open the folder on GitHubat commit 36726ae

Compare with similar skills

Atmos AWS Security next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Atmos AWS Security compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Atmos AWS Security this skillcloudposse/atmos	1.4k	—	~867	Automated safety check: Pass	Apache-2.0	today
Dd AWS Integrationdatadog-labs/agent-skills	177	—	~6.8k	Automated safety check: Notes	MIT	today
Config Scanjwynia/agent-skills	166	—	~2k	Automated safety check: Notes	MIT	7 mo ago
Agent Bom Scan InfraLeoYeAI/openclaw-master-skills	2.2k	—	~1.5k	Automated safety check: Pass	Apache-2.0	2 mo ago
Security Analyzeraiskillstore/marketplace	430	—	~1.2k	Automated safety check: Notes	None	yesterday
AWS Cloud Advisortech-leads-club/agent-skills	7k	—	~2.1k	Automated safety check: Pass	CC-BY-4.0	18 days ago

Similar skills

Dd AWS Integration
datadog-labs/agent-skills
Set up the Datadog AWS integration with Terraform - creates the cross-account IAM role Datadog assumes (external ID, no stored credentials), attaches the permission policies Datadog publishes, and…
177 GitHub stars~6.8k tokensUpdated today
DevOps & CloudAuto-check: notes
Config Scan
jwynia/agent-skills
Detect security misconfigurations in config files, Docker, and IaC.
166 GitHub stars~2k tokensUpdated 7 mo ago
DevOps & CloudAuto-check: notes
Agent Bom Scan Infra
LeoYeAI/openclaw-master-skills
Scan infrastructure-as-code, cloud configurations, and find secrets.
2.2k GitHub stars~1.5k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Security Analyzer
aiskillstore/marketplace
Comprehensive security vulnerability analysis for codebases and infrastructure.
430 GitHub stars~1.2k tokensUpdated yesterday
SecurityAuto-check: notes
AWS Cloud Advisor
tech-leads-club/agent-skills
Answers AWS architecture, security and service-selection questions by searching AWS documentation through MCP tools first, then adapting advice to your stack and team.
7k GitHub stars~2.1k tokensUpdated 18 days ago
DevOps & CloudAuto-check passed
Cloud Misconfig Auditor
criptogus/agent-evolve-network
Audits AWS, GCP and Azure environments (and matching IaC) for excessive permissions, public exposure, weak encryption defaults and missing logging.
288 GitHub stars~965 tokensUpdated 29 days ago
DevOps & CloudAuto-check passed

Questions about Atmos AWS Security

What does Atmos AWS Security do?

AWS security finding analysis: analyze findings, map to Atmos components/stacks, generate structured remediation with exact Terraform changes and deploy commands. Atmos AWS Security is an agent skill from cloudposse/atmos.

When should I use Atmos AWS Security?

Atmos AWS Security fits situations like: tasks that involve Cloud security; tasks that involve Infrastructure as code.

How do I install Atmos AWS Security in Claude Code?

Run `npx skills add cloudposse/atmos --skill atmos-aws-security -a claude-code`. Or copy the skill folder (agent-skills/skills/atmos-aws-security in cloudposse/atmos) into .claude/skills/atmos-aws-security in your project. Claude Code loads it when a task matches its description.

How do I install Atmos AWS Security in Codex?

Run `npx skills add cloudposse/atmos --skill atmos-aws-security -a codex`. Or copy the skill folder (agent-skills/skills/atmos-aws-security in cloudposse/atmos) into .agents/skills/atmos-aws-security in your project. Codex loads it when a task matches its description.

Can I use Atmos AWS Security in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cloudposse/atmos --skill atmos-aws-security -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atmos-aws-security, .gemini/skills/atmos-aws-security, .github/skills/atmos-aws-security and .opencode/skills/atmos-aws-security in your project.

What does Atmos AWS Security need to run?

SKILL.md names no scripts, command-line tools or credentials: Atmos AWS Security is instructions for the agent only.

Does Atmos AWS Security access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Atmos AWS Security safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Atmos AWS Security use?

Atmos AWS Security is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Atmos AWS Security use?

About 867 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Atmos AWS Security?

Skills that share tags, products or a category with Atmos AWS Security: Dd AWS Integration (datadog-labs/agent-skills, 177 stars), Config Scan (jwynia/agent-skills, 166 stars), Agent Bom Scan Infra (LeoYeAI/openclaw-master-skills, 2.2k stars) and Security Analyzer (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atmos AWS Security?

cloudposse (a GitHub organization) maintains it in cloudposse/atmos, which has 1,396 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 8, 2026.

Source: cloudposse/atmos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Atmos AWS Security

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Atmos AWS Security Finding Analysis

Output Format

Root Cause

Steps

Code Changes

Stack Changes

Deploy

Risk

References

Context You Receive

Analysis Guidelines

Files

Compare with similar skills

Similar skills

More from cloudposse/atmos

Related

Questions about Atmos AWS Security