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/sumonmselim/agentguard/awsnpx skills add SumonMSelim/agentguard --skill awsgit clone --depth 1 https://github.com/SumonMSelim/agentguardWrote 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/sumonmselim/agentguard/aws)<a href="https://agentmods.dev/skills/sumonmselim/agentguard/aws"><img src="https://agentmods.dev/badge/skills/sumonmselim/agentguard/aws.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 | $0.00032 | $0.00947 |
| Opus 5 | $0.00016 | $0.00474 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
aws 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS
Account structure
- Separate AWS accounts per environment (dev, staging, prod). Never share prod account
- AWS Organizations with SCPs for org-wide guardrails. Control Tower for multi-account setup
- Dedicated logging/security account. Ship CloudTrail, Config, and GuardDuty findings there
- SCPs: deny root usage, deny disabling CloudTrail/GuardDuty, enforce region restrictions
IAM
- Least privilege. No wildcard actions/resources (
*) in production - No long-lived human access keys. Use IAM Identity Center, roles, temp credentials
- EC2/Lambda/ECS: instance profiles and execution roles. Never credentials in code or env vars
- EKS: IRSA (IAM Roles for Service Accounts) per pod. No node-level roles for app permissions
- Separate roles per service and environment. No shared roles across workloads
- Permission boundaries for delegated admin. Prevents privilege escalation via role creation
- MFA on all IAM users. Root locked — never used
- Rotate credentials. Audit via IAM Access Analyzer. Remove unused permissions
Secrets
- Store in Secrets Manager or SSM Parameter Store (SecureString). Never in env vars, AMIs, images, Terraform state, or CloudFormation parameters (use SSM/Secrets Manager references)
- Auto-rotate via Secrets Manager rotation lambdas
- Reference by ARN in task definitions and Lambda config. Never pass values directly
Networking
- VPC per environment. Public subnets: load balancers only. Private: compute and data
- Security groups: ingress from known sources only. No
0.0.0.0/0except ALB port 443 - WAF in front of ALB and CloudFront for all public-facing workloads
- No EC2 public IPs unless required. Session Manager for all access — no SSH
- NACLs as secondary subnet-level layer
- VPC Flow Logs enabled. Ship to CloudWatch or S3
- PrivateLink for AWS service access where internet routing is avoidable
Security
- CloudTrail in all regions. Logs to dedicated locked-down S3 bucket
- GuardDuty enabled. Security Hub enabled with baseline standard (AWS Foundational or CIS)
- Macie enabled on S3 buckets containing sensitive or PII data
- S3: block public access at account level. Explicit bucket policies only
- S3 versioning + MFA delete on sensitive buckets
- S3 lifecycle policies: transition to IA/Glacier, expire old versions. Unbounded storage compounds cost
- KMS: customer-managed keys (CMK) for sensitive data at rest. Audit key usage
- Config enabled with conformance packs for drift detection
- ECR: image scanning on push. Block deploy on critical/high CVEs
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.
- 4d ago First seen · 74 lines · 0 tokens per session scan A 3ee1a1c1be03
aws is a skill published in the GitHub repository SumonMSelim/agentguard (56 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 947 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-30.
Other skills, from other repositories
cloudbase
腾讯云开发 CloudBase 全栈开发技能，覆盖 Web/小程序/uni-app 前端、云函数、云数据库、云存储与内置大模型能力，提供从接入到部署的全流程指导。.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
rule
Skill "rule" from x-cmd/x-cmd, covering rule — rules to rule, 核心命令, 规则文件格式, 示例 and 验证规则文件格式.
cve
Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.