What is aws-scan-security?

A security review of an Amazon Web Services (AWS) account that checks access controls, public exposure, and the status of security services.

Use it to inspect root and user access, IAM policies and keys, public S3 buckets and RDS databases, exposed security groups, and services such as CloudTrail and GuardDuty.

It highlights risks such as missing multi-factor authentication, old access keys, public storage or databases, and open network ports without changing the account.

aws-scan-security — Skill for Claude Code by nirecom/agents

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 nirecom/agents --skill aws-scan-security

Clone the repo

git clone --depth 1 https://github.com/nirecom/agents

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nirecom/agents/aws-scan-security/github.svg)](https://agentmods.dev/skills/nirecom/agents/aws-scan-security)

Your own site

<a href="https://agentmods.dev/skills/nirecom/agents/aws-scan-security"><img src="https://agentmods.dev/badge/skills/nirecom/agents/aws-scan-security/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nirecom/agents/aws-scan-security"><img src="https://agentmods.dev/badge/skills/nirecom/agents/aws-scan-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 464 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00022	$0.00464
Opus 5.5	$0.00009	$0.00186
Sonnet 5.5	$0.00004	$0.00093
Haiku 4.5	$0.00002	$0.00046

Measured 21d ago against content hash d1495dc67240, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aws-scan-security 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 21d 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.

skills/aws-scan-security/SKILL.md · 36 lines

What it actually says

Procedure

ASE-1. Verify prerequisites. ASE-2. IAM posture (pass --profile $AWS_PROFILE --region $AWS_DEFAULT_REGION):

Root MFA: aws iam get-account-summary --query 'SummaryMap.AccountMFAEnabled'
Users without MFA: aws iam list-virtual-mfa-devices --assignment-status Unassigned
Admin policies on users: aws iam list-attached-user-policies per user, flag AdministratorAccess
Access keys >90 days: aws iam list-access-keys, check CreateDate ASE-3. Public exposure:
Public S3: aws s3api get-bucket-acl + aws s3api get-bucket-policy-status per bucket
SGs 0.0.0.0/0 on 22/3389/3306/5432: aws ec2 describe-security-groups --filters Name=ip-permission.cidr,Values=0.0.0.0/0
Public RDS: aws rds describe-db-instances --query 'DBInstances[?PubliclyAccessible==\true`]'ASE-4. Security services: CloudTrail, GuardDuty, AWS Config, Security Hub (describe/list/get commands) ASE-5. Write raw findings to$AWS_STATE_DIR/security-.json(severity: critical/high/medium/low). ASE-6. Write human-readable summary to$AWS_STATE_DIR/security-.md`:
Severity table: critical/high/medium/low counts
One bullet per finding category (no identifiers) ASE-7. Print: counts by severity only — no identifiers.

Rules

Read-only only. Identifiers must NOT appear in conversation.
Critical findings must be highlighted.
AccessDeniedException → mark as unknown (not pass).

Skip Conditions

Skip if $AWS_STATE_DIR/security-<YYYYMMDD>.json exists and is less than 4 hours old.

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.

21d ago Changed · -1 lines d1495dc67240
1mo ago First seen · 37 lines · 22 tokens per session scan A 1e29642a2f06

Subscribe to this mod's changes

aws-scan-security is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 464 once invoked, about $0.0001 per session on Opus 5.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-31.

Security

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens