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 agentmods add skills/cookiemonsterdev/agents-skills/aws-iam-docsnpx skills add cookieMonsterDev/agents-skills --skill aws-iam-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWrote 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/cookiemonsterdev/agents-skills/aws-iam-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/aws-iam-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/aws-iam-docs.svg" alt="Measured on agentmods" 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.00089 | $0.01276 |
| Opus 5 | $0.00044 | $0.00638 |
| Sonnet 5 | $0.00018 | $0.00255 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
aws-iam-docs 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 6d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS IAM questions are easy to answer from stale memory or overly broad * permissions. Use this skill to ground answers in the official AWS IAM documentation and return the closest authoritative page instead of improvising security policy advice.
When to Use
Use this skill when the request is about:
- IAM concepts: principals, authentication, authorization, and policies
- IAM users, groups, roles, and identity federation
- Identity-based policies, resource-based policies, and permission boundaries
- Trust policies, assume-role, and cross-account access
- AWS STS temporary credentials and session policies
- IAM Identity Center (SSO) users, permission sets, and assignments
- MFA, access keys, and credential management best practices
- Service-linked roles and service roles
- IAM Access Analyzer, policy validation, and least-privilege guidance
- IAM Roles Anywhere and workload identity outside AWS
- Organizations SCPs when documented in IAM context (delegated admin, etc.)
- Troubleshooting access denied, implicit denies, and policy evaluation logic
Do not use this skill for:
- AWS CLI install, profiles, or
aws configure ssosyntax. Useaws-cli-docsinstead. - Service-specific resource configuration when the question is not about IAM permissions (for example S3 bucket lifecycle rules). Use the relevant service skill.
- Kubernetes RBAC on EKS. Use
kubernetes-docsoraws-eks-docsfor cluster RBAC; use this skill for AWS IAM side. - Application code using AWS SDK credential providers unless the question is about IAM roles/policies documented in IAM guides.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started and core concepts
- Users, groups, and long-term credentials
- Roles, trust policies, and temporary credentials
- Policies: JSON structure, actions, resources, conditions
- IAM Identity Center and federation
- MFA and credential security
- Cross-account access and delegation
- Access Analyzer and policy tools
- Service-linked roles and AWS service permissions
- Troubleshooting access denied and policy simulation
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 111 lines · 89 tokens per session scan A 3f0c1621efef
aws-iam-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 16d ago), licensed MIT. It adds 89 tokens to every session and 1,276 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-31.
Other skills, from other repositories
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
google-cloud-solution-n-tier-serverless-web-app
Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust…
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).