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 commands/hermeticormus/libresecops-claude-code/aws-sec-auditgit 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/commands/hermeticormus/libresecops-claude-code/aws-sec-audit)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/aws-sec-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/aws-sec-audit.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.01178 |
| Opus 5 | $0.00000 | $0.00589 |
| Sonnet 5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
aws-sec-audit 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aws-sec-audit
Structured security audit of AWS configuration covering IAM, S3, VPC, CloudTrail, and common misconfigurations.
Trigger
Use when you need to:
- Review AWS infrastructure configuration for security gaps
- Audit Terraform, CloudFormation, or CDK templates before deployment
- Prepare for a compliance audit or security review
- Validate that security controls are properly configured after changes
- Investigate whether an AWS environment follows security best practices
Input
One of:
- Live environment: AWS CLI access with read-only permissions (SecurityAudit managed policy or equivalent)
- Infrastructure-as-code: Terraform files (
.tf), CloudFormation templates (.yaml/.json), CDK code - Configuration export: Output from
aws iam get-account-authorization-details, Security Hub findings, Prowler reports - Specific scope: Focus area if not a full audit (e.g., "IAM only", "S3 buckets", "network exposure")
Process
Phase 1: Identity & Access Management
-
Root account security
- MFA enabled on root (
aws iam get-account-summary-- checkAccountMFAEnabled) - No root access keys (
aws iam get-account-summary-- checkAccountAccessKeysPresent) - Root usage in CloudTrail (should be near zero)
- MFA enabled on root (
-
IAM policies
- Scan for
"Effect": "Allow", "Action": "*", "Resource": "*"(full admin) - Check for inline policies vs managed policies (prefer managed)
- Identify unused IAM roles and users (
aws iam generate-credential-report) - Review cross-account trust relationships in role assume-role policies
- Check for
iam:PassRolewith wildcard resource (privilege escalation vector)
- Scan for
-
Access keys
- Age of access keys (>90 days is a finding)
- Users with multiple active access keys
- Access keys on root account (should not exist)
-
Password policy
- Minimum length >= 14 characters
- Complexity requirements enabled
- Password reuse prevention (remember >= 24)
Phase 2: Storage Security
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 · 145 lines · 0 tokens per session scan A 781df3627a1e
aws-sec-audit is a command 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 1,178 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 commands, from other repositories
build-mcp
Build a remote MCP server on Cloudflare using McpAgent.
build-agent
Build an AI agent on Cloudflare using the Agents SDK.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.