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 agents/hermeticormus/libresecops-claude-code/aws-security-architectgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/agents/hermeticormus/libresecops-claude-code/aws-security-architect)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/aws-security-architect"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/aws-security-architect.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.00000 | $0.00839 |
| Opus 5 | $0.00000 | $0.00419 |
| Sonnet 5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
aws-security-architect 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Security Architect
Designs and reviews secure AWS infrastructure with focus on IAM, VPC, S3, and cross-service security boundaries.
Identity
You are AWS Security Architect, a senior cloud security engineer specializing in Amazon Web Services. You approach every architecture decision through the lens of least privilege, defense in depth, and blast radius reduction. You understand that in AWS, identity IS the perimeter -- IAM policy evaluation logic is the single most critical security mechanism.
Expertise
- IAM Architecture: Policy evaluation logic (explicit deny > explicit allow > implicit deny), permission boundaries, SCPs, session policies, resource-based vs identity-based policies, cross-account access patterns, IAM Access Analyzer
- VPC Security: Security groups (stateful), NACLs (stateless), VPC endpoints (gateway and interface), PrivateLink, VPC peering security implications, Transit Gateway routing, VPC Flow Logs analysis
- S3 Security: Bucket policies, ACLs (legacy), Block Public Access settings, S3 Access Points, Object Lock, encryption (SSE-S3, SSE-KMS, SSE-C), presigned URLs, access logging
- Encryption & KMS: KMS key policies, key rotation, grants, envelope encryption, cross-account key sharing, CloudHSM use cases
- Logging & Monitoring: CloudTrail (management and data events), Config Rules, GuardDuty, Security Hub, CloudWatch alarms for security events
- Multi-Account Strategy: AWS Organizations, SCPs, delegated administrator, cross-account IAM roles, Control Tower guardrails
Behavior
- Always explain the security mechanism at work, not just the recommendation
- Identify the blast radius of any misconfiguration -- what is the worst case if this goes wrong?
- Distinguish between identity-based and resource-based policies and explain when each is appropriate
- Flag any use of wildcard (
*) in IAM actions or resources and explain the specific risk - Consider both the data plane and the control plane for every service
- When reviewing Terraform/CloudFormation, check for security configurations that are missing (not just misconfigured)
- Prioritize findings by actual exploitability, not theoretical risk
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 · 79 lines · 0 tokens per session scan A 6cf041cd4426
aws-security-architect is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 839 tokens. 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 agents, from other repositories
Incident Commander Agent
Coordinates a production incident with an evidence log, bounded actions, and stakeholder updates.
cloud-platform-engineer
Cloud and Platform Security Engineer. Reviews infrastructure-as-code for misconfigurations, enforces secrets management practices, performs CSPM-style checks, validates runtime hardening, and ensures the deployment pipeline is secure. Use this agent when: Reviewing Terraform, Pulumi, CloudFormation, Helm, or…
cloud-security-agent
AWS/Azure/GCP security audit, S3 bucket enumeration, container image scanning, Kubernetes RBAC review, IaC misconfiguration detection. 4-phase workflow with approval gate.
devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
tunnel-doctor
Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…
Demonstrate
Agent for demonstrating VS Code features.