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.
npx skills add niels-emmer/myace --skill aws-security-checklistgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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.
[](https://agentmods.dev/skills/niels-emmer/myace/aws-security-checklist)<a href="https://agentmods.dev/skills/niels-emmer/myace/aws-security-checklist"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/aws-security-checklist/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.
<a href="https://agentmods.dev/skills/niels-emmer/myace/aws-security-checklist"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/aws-security-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00037 | $0.00815 |
| Opus 5 | $0.00018 | $0.00407 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
AWS Security Checklist 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
A fast, consistent pass over an AWS infrastructure change to catch the
AWS-recommended security-practice violations that are easy to miss in a large
plan or diff — before it ever reaches the point of asking a human to approve
an apply. This is the AWS-specific companion to iac-expert's generic
iac-security-checklist, adding the AWS constructs (IAM, security groups,
private subnets, KMS, Secrets Manager, Security Hub/GuardDuty/Config,
CloudTrail) that the generic checklist can't name.
When to use it
Run this against every nontrivial AWS change (new resources, modified network/identity/access configuration) before handing it off for review or requesting apply approval. For a trivial change (a tag fix, a variable rename with no resource impact), a quick skim is enough.
Checklist
Mark each item PASS, FAIL, or N/A. Every FAIL needs either a fix or a
documented exception (see iac-expert's exception-documentation skill)
before the change moves forward.
Identity and access
- Service-to-service and CI/CD auth uses IAM roles and identity federation (IAM Roles Anywhere, OIDC federation), not long-lived access keys.
- Any IAM policy is scoped to least privilege (specific actions/resources,
not
AdministratorAccess/*) and uses AWS-managed policies where possible. - Human access is behind IAM with MFA — no shared accounts, no standing root/access-key credentials in code or config.
- Secrets that must exist live in Secrets Manager (or SSM Parameter Store),
referenced by ID — never embedded as a literal in
.tf, a tfvars file, or a module default.
Network
- No resource has a public IP, public endpoint, or
0.0.0.0/0-equivalent security-group rule unless it's a documented exception. - Workloads run in private subnets; AWS services are reached via VPC endpoints where supported, keeping traffic off the public internet.
- Inter-service traffic that could stay on a private VPC does; security groups/NACLs default to deny and open only what's needed.
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.
- 10d ago First seen · 78 lines · 37 tokens per session scan A 3d0d089203ba
AWS Security Checklist is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 815 once invoked, about $0.0002 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-31.
Other skills, from other repositories
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability.
cis-aws-compute-2.3
Ensure Tag Policies are Enabled.
design-aws-terraform-iac
Designs AWS-targeted Terraform infrastructure plans before implementation. Focuses on service selection, module boundaries, state/backends, environment separation, security/compliance guardrails, acceptance criteria, and explicit risk/validation assumptions.
loom-terraform
Infrastructure as Code with Terraform/OpenTofu.