Skip to content
TrustedSkillsbeta
Back to all skills

Aws Penetration Testing

Listed
dokhacgiakhoa·vlatest·cloud

Helps with AWS, testing as part of deploying and managing cloud infrastructure workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it AWS Penetration Testing, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add dokhacgiakhoa/agent-skills-4-vibe-coding-cli --skill "AWS Penetration Testing" -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dokhacgiakhoa

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    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.

  • 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 dokhacgiakhoa/antigravity-ide at c4a059bbf7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c4a059bbf7
Manifest
.agent/skills/aws-penetration-testing/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to perform penetration testing on AWS environments. It identifies vulnerabilities and misconfigurations within an AWS infrastructure, providing detailed reports of potential security risks. The tool aims to simulate real-world attack scenarios to assess the robustness of cloud deployments.

When to use it

  • Security Audits: Regularly evaluate the security posture of your AWS environment before or after significant changes.
  • New Deployment Validation: Ensure new applications and services deployed on AWS are secure by design.
  • Compliance Checks: Verify adherence to industry best practices and regulatory requirements related to cloud security.
  • Incident Response Preparation: Simulate attacks to test incident response plans and identify areas for improvement.

Key capabilities

  • Vulnerability scanning
  • Misconfiguration detection
  • Report generation
  • Attack simulation

Example prompts

  • "Perform a penetration test on my AWS account, focusing on S3 bucket permissions."
  • "Scan my VPC configuration for potential security weaknesses and report any findings."
  • "Simulate an attack targeting EC2 instances with public IP addresses in the us-east-1 region."

Tips & gotchas

This skill requires appropriate AWS credentials with sufficient permissions to access and scan resources. Be aware that penetration testing can potentially disrupt services, so it's recommended to perform scans during non-peak hours or in a staging environment first.