Aws Penetration Testing
ListedHelps with AWS, testing as part of deploying and managing cloud infrastructure workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add sickn33/agentic-awesome-skills --skill aws-penetration-testing -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
sickn33
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 3 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: 169.254.169.254, 169.254.170.2, app.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
169.254.169.254undeclared169.254.170.2undeclaredapp.comundeclaredWhat it found (3 of 8)
- plugins/agentic-awesome-skills-claude/skills/aws-penetration-testing/SKILL.md:113contacts 169.254.169.254
http://169.254.169.254/latest/meta-data/ - plugins/agentic-awesome-skills-claude/skills/aws-penetration-testing/SKILL.md:116contacts 169.254.169.254
http://169.254.169.254/latest/meta-data/iam/security-credentials/ - plugins/agentic-awesome-skills-claude/skills/aws-penetration-testing/SKILL.md:119contacts 169.254.169.254
http://169.254.169.254/latest/meta-data/iam/security-credentials/ROLE-NAME
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned sickn33/antigravity-awesome-skills at 5a4cdd9df8.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 5a4cdd9df8
- Scanned
- 1 file, 386 lines
- Copies in repo
- 3 — all of them scanned
About this skill
The aws-penetration-testing skill empowers AI agents to conduct comprehensive security assessments of AWS environments. It automates the discovery of vulnerabilities and misconfigurations across cloud resources to harden infrastructure defenses.
When to use it
- Performing pre-deployment security audits on new AWS architectures before going live.
- Identifying exposed S3 buckets or open security groups in production environments.
- Validating compliance with security best practices after major infrastructure changes.
- Simulating attacker techniques to test the resilience of cloud-native applications.
Key capabilities
- Scans for common AWS misconfigurations and insecure settings.
- Identifies unpatched software and outdated dependencies within EC2 instances.
- Detects overly permissive IAM roles and policies that grant excessive access.
- Analyzes network topology to find potential lateral movement paths.
Example prompts
- "Run a full penetration test on my AWS account focusing on S3 bucket permissions and security group rules."
- "Identify any EC2 instances with open SSH ports or outdated operating systems in the us-east-1 region."
- "Generate a report of IAM policies that allow wildcard access to DynamoDB tables."
Tips & gotchas
Ensure you have explicit authorization before running penetration tests on production environments to avoid accidental service disruption. Always configure AWS CloudTrail and GuardDuty to monitor for anomalous activity triggered by the testing process.