pentesting-with-aws-security-agent

pentesting-with-aws-security-agent is a skill for Claude Code from aws/agent-toolkit-for-aws. It costs 85 tokens per session (1,627 once invoked), scanned A, original, Apache-2.0.

A workflow for running a penetration test, an authorized attempt to find security weaknesses, against a live web application using AWS Security Agent. It registers the target, runs tests against its endpoints, and reports verified findings.

In plain words
What is it for?
Testing an authorized running web application, probing its supplied endpoints, and collecting the resulting security findings. Tests can take from one hour to a day.
Why use it?
It organizes the setup and execution of an active security test, including the AWS values and target details needed to run it.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the aws-agents-for-devsecops plugin — 13 skills, 9 commands, 1 MCP server shipped together

Good fit Testing an authorized running web application, probing its supplied endpoints, and collecting the resulting security findings. Tests can take from one hour to a day.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aws/agent-toolkit-for-aws/pentesting-with-aws-security-agent
About the project

Agent Toolkit for AWS is a collection of AWS-supported MCP servers, skills, plugins, commands, and hooks that help AI coding agents build, deploy, and manage applications on AWS. It is used by developers working with AWS services through agents such as Claude Code, Codex, Cursor, and Kiro. The catalogue entries are the toolkit's own agent extensions for AWS development and operations.

aws/agent-toolkit-for-aws · 2,550 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add aws/agent-toolkit-for-aws --skill pentesting-with-aws-security-agent
Clone the repo
git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws

Made for: Claude Code.

Or install aws-agents-for-devsecops, the plugin that ships this one along with the rest of its 13 skills, 9 commands, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pentesting-with-aws-security-agent

README.md
[![agentmods](https://agentmods.dev/badge/skills/aws/agent-toolkit-for-aws/pentesting-with-aws-security-agent.svg)](https://agentmods.dev/skills/aws/agent-toolkit-for-aws/pentesting-with-aws-security-agent)
Your own site
<a href="https://agentmods.dev/skills/aws/agent-toolkit-for-aws/pentesting-with-aws-security-agent"><img src="https://agentmods.dev/badge/skills/aws/agent-toolkit-for-aws/pentesting-with-aws-security-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,627 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket warn 18 Jun 2026
  • Snyk pass 18 Jun 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.01627
Opus 5 $0.00043 $0.00813
Sonnet 5 $0.00017 $0.00325
Haiku 4.5 $0.00009 $0.00163

Measured 7d ago against content hash 14ed122942f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

pentesting-with-aws-security-agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/aws-agents-for-devsecops/skills/pentesting-with-aws-security-agent/SKILL.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AWS Security Agent — Penetration Test

This skill handles pentest setup, execution, and findings. Initial Security Agent setup (agent space, role, bucket) is handled by the setup-security-agent skill — if .security-agent/config.json is missing, the pentest workflow auto-runs setup inline first.

Pentests are slow (1-24 hours) and active — they probe a real running app. Always confirm the user is authorized to test the target before starting.


Resolving the values you need

The CLI examples below use placeholders. Resolve them at the start of every pentest:

Placeholder How to resolve
<id> (agent space) config.agent_space_id
<region> config.region (default us-east-1)
<account> aws sts get-caller-identity --query Account --output text (cache for the rest of the turn)
<role-arn> arn:aws:iam::<account>:role/SecurityAgentScanRole
<td-id> targetDomainId returned by create-target-domain (cache under config.target_domains[<domain>])
<pentest-id> pentestId returned by create-pentest
<pj-id> pentestJobId returned by start-pentest-job

Pre-pentest checks

  1. Read .security-agent/config.json. If missing → tell the user one line — "First pentest in this workspace — running setup first." — and run the setup-security-agent workflow inline before continuing.

  2. Verify agent space still exists:

    aws securityagent batch-get-agent-spaces --agent-space-ids <id>
    

    If missing, clear agent_space_id from config.json and run setup-security-agent again.

  3. Resolve account and role ARN from the table above.

  4. Authorization check: ask the user "Do you own or have explicit permission to pentest <target>?" if it's not obvious from context. Do not proceed without confirmation.


Workflow

1. Register target domain (one-time per domain)

aws securityagent create-target-domain --agent-space-id <id> \
  --target-domain-name <domain> --verification-method HTTP_ROUTE

Read the full file on GitHub · 158 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 158 lines · 85 tokens per session scan A 14ed122942f8

Subscribe to this mod's changes

pentesting-with-aws-security-agent is a skill published in the GitHub repository aws/agent-toolkit-for-aws (2,550 stars, last pushed 2d ago), licensed Apache-2.0. It adds 85 tokens to every session and 1,627 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens