Cloud Audit
briiirussell/cybersecurity-skills
Audit cloud infrastructure (AWS, GCP, Azure) for misconfigurations, excessive permissions, and security gaps.
Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1/ASFF) controls and…
Install AWS Security
$ npx skills add aws/agent-toolkit-for-aws --skill aws-security -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-security --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/core-skills/aws-security .claude/skills/aws-security && rm -rf skills-srcUse ~/.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/
Install the "aws-security" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-security into .claude/skills/aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 install https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-securityType 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.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-security -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-security --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/core-skills/aws-security .agents/skills/aws-security && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aws-security" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-security into .agents/skills/aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-security -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-security --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/core-skills/aws-security .cursor/skills/aws-security && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "aws-security" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-security into .cursor/skills/aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 https://github.com/aws/agent-toolkit-for-aws.git --path skills/core-skills/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.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-security -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-security --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/core-skills/aws-security .gemini/skills/aws-security && rm -rf skills-srcUse ~/.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/
Install the "aws-security" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-security into .gemini/skills/aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ gh skill install aws/agent-toolkit-for-aws aws-securityInstalls 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).
$ npx skills add aws/agent-toolkit-for-aws --skill aws-security -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/core-skills/aws-security .github/skills/aws-security && rm -rf skills-srcUse ~/.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/
Install the "aws-security" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-security into .github/skills/aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-security -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-security --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/core-skills/aws-security .opencode/skills/aws-security && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "aws-security" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-security into .opencode/skills/aws-security/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
aws-security- GitHub stars
- 2.8k
- Token cost
- ~3.4k tokens
- SKILL.md length
- 1,408 words
- Files
- 24 (incl. references)
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1/ASFF) controls and…
- Works in 9 steps: Read-only APIs only. This skill and all… → No severity judgements on configuration… → No false-positive suppression… → …
- Tasks that involve Cloud security
- SKILL.md covers Global rules, How this skill works, Sub-skill registry and Disambiguation, plus 2 more sections
- Calls aws
What it does
AWS Security is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1/ASFF) controls and compliance standards; GuardDuty threat findings; Inspector vulnerability findings; Macie sensitive data findings; Detective investigation; and Security Lake configuration and data aggregation. Applicable when questions involve security posture, Exposure findings, CSPM failed controls, threat findings, vulnerability…
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 24 other files, including reference files (for example `references/detective-configuration.md`, `references/detective-investigations.md` and `references/detective.md`).
It sits in Security, covering Cloud security. It works with Amazon Web Services and Model Context Protocol. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Cloud security
Example prompts
- “Use the aws-security skill to cover AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation…”
- “/aws-security”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Read-only APIs only. This skill and all its references use exclusively non-mutating APIs. NEVER reference, recommend, or invoke any API…
- No severity judgements on configuration state. Present what is and is not configured factually. Do not assign severity labels, gap…
- No false-positive suppression recommendations. Focus on helping customers understand findings. Do not recommend suppression filters…
- Prioritize Attack Sequences in GuardDuty. Findings with type prefix AttackSequence: represent correlated multi-step attacks. Always…
- Prioritize Exposure findings in Security Hub. Exposure findings (attack paths, resource exposure) represent Security Hub's unique…
- Expensive operations require explicit request. MUST NOT paginate through all member accounts by default. Per-account enumeration only…
- Match the user's language. Respond in the same language the user writes in.
- Verify, don't guess. If you cannot confirm a fact from a reference file or API output, say so.
- Sensitive data disclosure. When a procedure produces output that may contain sensitive information (full finding bodies, IP addresses…
What it can do on your machine
Read from SKILL.md and the folder at commit 188af2f. 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
Shell commands in SKILL.md call:
aws
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.aws.amazon.com
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
AWS Security loads about 3.4k tokens when it runs, and up to ~28k if it reads all its reference files. Until then it costs about 181 tokens; SKILL.md has 1,408 words of instructions outside code blocks.
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 aws/agent-toolkit-for-aws at commit 188af2f, republished under its Apache-2.0 licence (© aws). 1,408 words, ~3,419 tokens.
Download SKILL.mdSave it as
.claude/skills/aws-security/SKILL.md (or your agent's skills folder). This skill also uses 23 other files; get the full folder from GitHub.- name
- aws-security
- description
- Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1/ASFF) controls and compliance standards; GuardDuty threat findings; Inspector vulnerability findings; Macie sensitive data findings; Detective investigation; and Security Lake configuration and data aggregation. Applicable when questions involve security posture, Exposure findings, CSPM failed controls, threat findings, vulnerability findings, sensitive data findings, automation rules, or cross-service security configuration across AWS environments. Procedures use standard AWS CLI syntax and work with or without the AWS MCP server.
- metadata.version
- 1
AWS Security
STOP — Do not answer from general knowledge. Before responding to any security service question, match the user's request against the sub-skill registry below and follow its procedure. If the procedure says to load a reference file, you MUST read it before providing operational guidance. Never skip the routing step.
AWS Security services provide threat detection (GuardDuty), vulnerability management (Inspector), unified security dashboard and exposure analysis (Security Hub), compliance posture management (Security Hub CSPM), sensitive data discovery (Macie), investigation (Detective), and centralized log storage (Security Lake). Each service has dedicated reference procedures for configuration review and findings/investigation summarization.
This skill works with or without the AWS MCP server. When available, the AWS MCP server is recommended for sandboxed execution and audit logging. Procedures use standard AWS CLI syntax (aws <service> <command>).
See references/services-overview.md for service relationships, data formats, and cross-service integration patterns.
Global rules
Read-only APIs only. This skill and all its references use exclusively non-mutating APIs. NEVER reference, recommend, or invoke any API that creates, modifies, deletes, enables, disables, or otherwise mutates resource state or configuration — not even in prose recommendations. See service reference files for the complete allowed API list.
No severity judgements on configuration state. Present what is and is not configured factually. Do not assign severity labels, gap assessments, or editorial framing (e.g., "critical gap", "security issue") to configuration state.
No false-positive suppression recommendations. Focus on helping customers understand findings. Do not recommend suppression filters, archival rules, or finding dismissal.
Prioritize Attack Sequences in GuardDuty. Findings with type prefix
AttackSequence:represent correlated multi-step attacks. Always surface these first, before severity breakdown.Prioritize Exposure findings in Security Hub. Exposure findings (attack paths, resource exposure) represent Security Hub's unique cross-service correlation. Surface these first in any findings summary.
Expensive operations require explicit request. MUST NOT paginate through all member accounts by default. Per-account enumeration only executes if the user explicitly requests detailed account-level information. Use statistics/count APIs where available (e.g.,
get-coverage-statistics).Match the user's language. Respond in the same language the user writes in.
Verify, don't guess. If you cannot confirm a fact from a reference file or API output, say so.
Sensitive data disclosure. When a procedure produces output that may contain sensitive information (full finding bodies, IP addresses, resource identifiers, network configurations, threat intelligence details), present a summary first. Note what sensitive data the full output contains. Display the complete raw response only when the caller explicitly requests it.
How this skill works
Find the sub-skill — Match the user's request against the sub-skill registry below. Match on meaning, not exact wording. If ambiguous, ask: "Are you checking configuration, or do you need a findings summary?"
If a sub-skill matches — read
references/{sub-skill-id}.mdand follow its procedure.If no sub-skill matches — answer from the service reference files listed below. Load
references/services-overview.mdfor cross-service context, or the relevant service reference file (e.g.,references/guardduty.md) for API scope and severity scoring questions.Cross-service overview — When the user asks about overall security posture across multiple services, start with
references/services-overview.md, then route to relevant sub-skills.
Sub-skill registry
| ID | Name | Trigger Phrases | When to Route Here | Reference |
|---|---|---|---|---|
guardduty-configuration | GuardDuty Config Review | "is GuardDuty configured", "check detector", "GuardDuty features enabled", "runtime monitoring setup" | User wants to verify GuardDuty deployment completeness | references/guardduty-configuration.md |
guardduty-findings | GuardDuty Findings Summary | "summarize GuardDuty findings", "what threats", "GuardDuty severity breakdown", "attack sequences" | User wants a findings posture snapshot | references/guardduty-findings.md |
inspector-configuration | Inspector Config Review | "is Inspector scanning", "Inspector enabled", "scan types", "coverage gaps" | User wants to verify Inspector deployment | references/inspector-configuration.md |
inspector-findings | Inspector Findings Summary | "vulnerabilities found", "Inspector findings", "CVE summary", "vulnerability posture" | User wants vulnerability overview | references/inspector-findings.md |
security-hub-configuration | Security Hub Config Review | "Security Hub integrations", "aggregation configured", "connectors", "automation rules", "V2 automation rules", "OCSF automation rules" | User wants to verify Security Hub V2 (OCSF) setup | references/security-hub-configuration.md |
security-hub-findings | Security Hub Findings Summary | "risk overview", "exposure findings", "attack paths", "OCSF findings", "security posture trends" | User wants Security Hub V2 (OCSF) findings overview | references/security-hub-findings.md |
security-hub-cspm-configuration | CSPM Config Review | "standards enabled", "controls", "FSBP", "CIS", "PCI-DSS", "NIST", "compliance setup", "AI security", "AI best practices", "CSPM automation rules", "ASFF automation rules" | User wants to verify compliance standards setup | references/security-hub-cspm-configuration.md |
security-hub-cspm-findings | CSPM Compliance Summary | "compliance posture", "failed controls", "pass rate", "ASFF findings", "third-party findings" | User wants compliance findings overview | references/security-hub-cspm-findings.md |
macie-configuration | Macie Config Review | "Macie configured", "data discovery setup", "classification jobs", "Macie enabled" | User wants to verify Macie deployment | references/macie-configuration.md |
macie-findings | Macie Findings Summary | "sensitive data found", "Macie findings", "data classification results", "PII detected" | User wants sensitive data overview | references/macie-findings.md |
detective-configuration | Detective Config Review | "Detective configured", "behavior graph", "Detective members", "data sources" | User wants to verify Detective deployment | references/detective-configuration.md |
detective-investigations | Detective Investigations Summary | "Detective investigations", "investigation status", "indicators", "finding groups" | User wants investigation landscape overview | references/detective-investigations.md |
security-lake-configuration | Security Lake Config Review | "Security Lake configured", "log sources enabled", "subscribers", "data lake setup" | User wants to verify Security Lake deployment | references/security-lake-configuration.md |
security-lake-sources | Security Lake Sources Summary | "what's flowing into Security Lake", "ingestion status", "source health", "data lake exceptions" | User wants data lake health overview | references/security-lake-sources.md |
organization-policies | Organization Policies Review | "organization policies", "org policies", "SECURITYHUB_POLICY", "INSPECTOR_POLICY", "list-policies", "policy targets", "policy enforcement" | User wants to review or discover AWS Organizations service policies | references/organization-policies.md |
Show full SKILL.md (545 more words)Show less
Disambiguation
| Keywords | Route to |
|---|---|
| "automation rules" (ambiguous) | Both Security Hub and Security Hub CSPM have automation rules. If customer uses Security Hub V2 (OCSF), route to Security Hub config. If customer uses Security Hub CSPM (ASFF), route to CSPM config. Ask if unclear. |
| "standards", "controls", "compliance", "FSBP", "CIS", "PCI", "NIST", "ASFF" | Security Hub CSPM skills |
| "integrations", "risk score", "attack path", "OCSF", "exposure", "connectors" | Security Hub skills |
| "threat detection", "GuardDuty", "detector", "runtime monitoring", "attack sequence" | GuardDuty skills |
| "vulnerability", "CVE", "Inspector", "scanning", "code vulnerability" | Inspector skills |
| "sensitive data", "classification", "Macie", "PII", "data discovery" | Macie skills |
| "investigation", "behavior graph", "Detective", "indicators" | Detective skills |
| "data lake", "log sources", "Security Lake", "subscribers", "ingestion" | Security Lake skills |
| "organization policies", "org policies", "policy type", "list-policies --filter" | Organization Policies (cross-service) |
Note: If a customer is using Security Hub V2 (OCSF), they should use Security Hub automation rules (list-automation-rules-v2) and should NOT use Security Hub CSPM features for new rules, even though CSPM remains technically available.
Service reference
Load service reference files on demand — only when the current turn requires context about service capabilities, API scope, or severity scoring.
| Reference | Content | When to Load |
|---|---|---|
references/services-overview.md | Cross-service relationships, data formats, membership models, admin discovery, API conventions | Cross-service questions, general security posture, "which services should I enable" |
references/guardduty.md | GuardDuty APIs, severity scoring, service notes | GuardDuty-specific questions about APIs or severity |
references/inspector.md | Inspector APIs, severity scoring, service notes | Inspector-specific questions about APIs or severity |
references/security-hub.md | Security Hub V2 (OCSF) APIs, severity scoring, service notes | Security Hub V2-specific questions about APIs or severity |
references/security-hub-cspm.md | Security Hub CSPM (V1/ASFF) APIs, severity scoring, service notes | CSPM-specific questions about APIs or severity |
references/macie.md | Macie APIs, severity scoring, service notes | Macie-specific questions about APIs or severity |
references/detective.md | Detective APIs, severity scoring, service notes | Detective-specific questions about APIs or severity |
references/security-lake.md | Security Lake APIs, service notes | Security Lake-specific questions about APIs |
references/organization-policies.md | Organization policies discovery pattern, policy types, Organizations APIs | Questions about org-level policy enforcement across security services |
Security considerations
- Logging and monitoring: Verify CloudTrail is enabled for security service and Organizations API calls, CloudTrail log file validation is active, and CloudWatch metric filters or alarms exist for anomalous privileged read patterns such as unexpected volume, unusual principals, or unexpected regions.
- Encryption and destinations: Verify publishing or export destinations such as S3 buckets, SNS topics, and CloudWatch Logs use KMS encryption at rest and TLS in transit. For downstream S3 or SNS destinations, verify resource policies use
aws:SourceArnandaws:SourceAccountcondition keys where applicable. - Notification recipients: Verify SNS topic subscriptions and other security alarm recipients are restricted to authorized security personnel, and periodically audit subscription endpoints.
- Credential management: Confirm CLI execution is using temporary credentials such as IAM roles or AWS SSO. Verify third-party integration credentials, API tokens, or connector secrets are stored in AWS Secrets Manager or AWS Systems Manager Parameter Store rather than plaintext configuration files or environment variables.
- Security references: Consult AWS Security Hub best practices, AWS CloudTrail security best practices, IAM security best practices, and the AWS Well-Architected Security Pillar for current service guidance.
- Sensitive data: Security service outputs may contain sensitive information such as IP addresses, resource identifiers, account IDs, vulnerability details, exposure paths, and threat intelligence. Classification and handling requirements are customer-specific; do not store or share outputs in unprotected channels without verifying organizational data handling policies.
© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 23 other files (references) in skills/core-skills/aws-security of aws/agent-toolkit-for-aws.
- SKILL.md
- references/detective-configuration.md
- references/detective-investigations.md
- references/detective.md
- references/guardduty-configuration.md
- references/guardduty-findings.md
- references/guardduty.md
- references/inspector-configuration.md
- references/inspector-findings.md
- references/inspector.md
- references/macie-configuration.md
- references/macie-findings.md
- references/macie.md
- references/organization-policies.md
- references/security-hub-configuration.md
- references/security-hub-cspm-configuration.md
- references/security-hub-cspm-findings.md
- references/security-hub-cspm.md
- references/security-hub-findings.md
- references/security-hub.md
- … and 4 more
Open the folder on GitHubat commit 188af2f
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| AWS Security this skillaws/agent-toolkit-for-aws | 2.8k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Cloud Auditbriiirussell/cybersecurity-skills | 413 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Ecs Operation Reviewaws/tools-for-devops-agent | 100 | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Iamitsmostafa/aws-agent-skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| AWS Security ArchitectureHack23/cia | 239 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| AWS Iamsickn33/agentic-awesome-skills | 47k | 2 repos | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Ecs Operation Review
aws/tools-for-devops-agent
Performs a comprehensive Amazon ECS operations review across the 6 review pillars (Resiliency & HA, Observability, Security, Operations, Performance, Additional Analysis) using read-only AWS APIs…
Iam
itsmostafa/aws-agent-skills
AWS Identity and Access Management for users, roles, policies, and permissions.
AWS Security Architecture
Hack23/cia
AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment
AWS Iam
sickn33/agentic-awesome-skills
Manage IAM users, roles, and policies. An agent skill from sickn33/agentic-awesome-skills.
Implementing Cloud Vulnerability Posture Management
mukul975/Anthropic-Cybersecurity-Skills
Implement multi-cloud CSPM to detect cloud-native misconfigurations and vulnerabilities (IAM over-permissions, exposed storage, unencrypted data, missing network controls) using AWS Security Hub…
More from aws/agent-toolkit-for-aws
All 138 skills in this repo- Official
Agent Advisor
aws/agent-toolkit-for-aws
Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.
- Official
Agents Build
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
- Official
Launch With AWS
aws/agent-toolkit-for-aws
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
- Official
Processing S3 Uploads With Step Functions
aws/agent-toolkit-for-aws
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
- Official
AWS Marketplace Metering
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
- Official
Agents Pay
aws/agent-toolkit-for-aws
A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.
Related
Categories
Questions about AWS Security
What does AWS Security do?
Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1/ASFF) controls and…. AWS Security is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1/ASFF) controls and compliance standards; GuardDuty threat findings; Inspector vulnerability findings; Macie sensitive data findings; Detective investigation; and Security Lake configuration and data aggregation.
When should I use AWS Security?
AWS Security fits situations like: tasks that involve Cloud security.
How do I install AWS Security in Claude Code?
Run `npx skills add aws/agent-toolkit-for-aws --skill aws-security -a claude-code`. Or copy the skill folder (skills/core-skills/aws-security in aws/agent-toolkit-for-aws) into .claude/skills/aws-security in your project. Claude Code loads it when a task matches its description.
How do I install AWS Security in Codex?
Run `npx skills add aws/agent-toolkit-for-aws --skill aws-security -a codex`. Or copy the skill folder (skills/core-skills/aws-security in aws/agent-toolkit-for-aws) into .agents/skills/aws-security in your project. Codex loads it when a task matches its description.
Can I use 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 aws/agent-toolkit-for-aws --skill 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/aws-security, .gemini/skills/aws-security, .github/skills/aws-security and .opencode/skills/aws-security in your project.
What does AWS Security need to run?
Going by SKILL.md and its folder, AWS Security needs the command-line tools its instructions call (aws).
Does AWS Security access the network?
SKILL.md names 1 domain. As links in the text: docs.aws.amazon.com. This is read from the text; nothing was executed.
Is 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 AWS Security use?
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 AWS Security use?
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 25k tokens, read only when the agent opens those files.
What are the alternatives to AWS Security?
Skills that share tags, products or a category with AWS Security: Cloud Audit (briiirussell/cybersecurity-skills, 413 stars), Ecs Operation Review (aws/tools-for-devops-agent, 100 stars), Iam (itsmostafa/aws-agent-skills, 1.2k stars) and AWS Security Architecture (Hack23/cia, 239 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains AWS Security?
aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,825 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 7, 2026.
Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.