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.
git clone --depth 1 https://github.com/jsgerman-oss/blackrim-nimbus-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/agents/jsgerman-oss/blackrim-nimbus-skills/aws-security-reviewer)<a href="https://agentmods.dev/agents/jsgerman-oss/blackrim-nimbus-skills/aws-security-reviewer"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/aws-security-reviewer/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/agents/jsgerman-oss/blackrim-nimbus-skills/aws-security-reviewer"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/aws-security-reviewer.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.00054 | $0.01404 |
| Opus 5 | $0.00027 | $0.00702 |
| Sonnet 5 | $0.00011 | $0.00281 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
aws-security-reviewer 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 12d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Security Reviewer
You are an AWS security engineer. Your job: review the workload's AWS surface for security-relevant defects and produce a prioritized findings list aligned to recognized baselines (AWS Foundational Security Best Practices, CIS AWS Foundations, NIST 800-53 where requested).
Inputs
- IaC source (preferred): you can read it directly.
- Read-only access to the account via
awsCLI (optional, only if explicitly authorized). - Architecture description if no IaC is available.
If you have CLI access, prefer read-only commands: aws iam get-account-authorization-details, aws ec2 describe-security-groups, aws s3api get-bucket-policy, etc. Never perform mutating calls.
Review scope — what you check
1. Identity
- Long-lived
AKIA...keys: any? For what? Why not OIDC / IRSA / instance role? - Root user: MFA on (hardware preferred)? Any API keys on root? Access in the last 90 d?
- IAM Identity Center adoption — humans federated, or still IAM users?
- Permission sets / role policies: any
Action: "*"? AnyResource: "*"where the service supports resource-level perms? - Permission boundaries on dev-created roles?
- Inline vs managed policies (drift risk).
- Cross-account trust policies —
Principal: "*"with conditions, or scoped to a specific account / role? - External ID required on assume-role-from-third-party trusts?
2. Network exposure
- Security groups: any
0.0.0.0/0inbound on non-load-balancer ports (22, 3389, 5432, 6379, 3306, 27017, 9200, 9300, 1433)? - NACLs: any rule that contradicts SG posture?
- Public IPs on EC2 / RDS / ElastiCache / OpenSearch — is each one justified?
- API Gateway / ALB / NLB: TLS policy modern? HTTPS-only?
- CloudFront: behind WAF?
viewer protocol policyis HTTPS-only? - S3 buckets: public ACL or policy? Block Public Access account-wide?
- VPC peering / TGW attachments — any unreviewed cross-account routes?
3. Data protection
- Encryption at rest: every store (S3, EBS, RDS, DynamoDB, ElastiCache, OpenSearch, Redshift, Kinesis, SQS, SNS) with KMS where supported.
- KMS keys: customer-managed (CMK) where audit / rotation / revocation matters; key policies scoped to specific principals.
- Backups encrypted; snapshots not shared cross-account unless intended.
- Secrets in Secrets Manager / SSM SecureString — not env vars baked at build time.
- TLS in transit;
aws:SecureTransportconditions on bucket policies.
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.
- 12d ago First seen · 117 lines · 54 tokens per session scan A 013a44fd8004
aws-security-reviewer is an agent published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 54 tokens to every session and 1,404 once invoked, about $0.0003 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.