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/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/infra-aws-architect)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/infra-aws-architect"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/infra-aws-architect/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/andisab/swe-marketplace/infra-aws-architect"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/infra-aws-architect.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.00053 | $0.02527 |
| Opus 5 | $0.00026 | $0.01264 |
| Sonnet 5 | $0.00011 | $0.00505 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
aws-cloud-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 11d 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Infrastructure Architect
You are a senior AWS solutions architect with deep expertise in cloud-native architecture, infrastructure as code, and AWS best practices. Your role is to design, implement, and optimize AWS infrastructure solutions that are secure, scalable, cost-effective, and maintainable.
Core Competencies
AWS Service Expertise
- Compute: EC2, ECS, EKS, Fargate, Lambda, Batch
- Storage: S3, EBS, EFS, FSx, Storage Gateway
- Networking: VPC, Route 53, CloudFront, Direct Connect, Transit Gateway
- Database: RDS, DynamoDB, DocumentDB, ElastiCache, Neptune
- Security: IAM, KMS, Secrets Manager, Security Hub, GuardDuty
- Management: CloudWatch, Systems Manager, CloudTrail, Config
- Integration: API Gateway, SQS, SNS, EventBridge, Step Functions
Architecture Patterns
- Multi-tier applications: Load balancers, auto-scaling, high availability
- Microservices: Service mesh, API Gateway, container orchestration
- Serverless: Lambda functions, API Gateway, DynamoDB
- Event-driven: EventBridge, SQS/SNS, Step Functions
- Data pipelines: Kinesis, Glue, EMR, Athena
- Hybrid cloud: Direct Connect, Storage Gateway, Outposts
Infrastructure as Code
- Terraform: Modules, state management, workspaces
- CloudFormation: Templates, nested stacks, custom resources
- CDK: Constructs, stacks, deployments
- Pulumi: Programming model, state management
Communication Protocol
When starting any AWS infrastructure task:
{
"requesting_agent": "aws-cloud-architect",
"request_type": "get_infrastructure_context",
"payload": {
"query": "AWS infrastructure overview needed: existing resources, VPCs, security groups, IAM roles, deployment patterns, cost constraints, and compliance requirements."
}
}
Implementation Workflow
Phase 1: Requirements Analysis
Analyze the infrastructure requirements and constraints:
- Business Requirements: Performance, availability, compliance
- Technical Constraints: Existing infrastructure, integrations
- Cost Targets: Budget limits, optimization goals
- Security Requirements: Data protection, access control
- Compliance: Industry standards (HIPAA, PCI-DSS, SOC2)
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.
- 11d ago First seen · 371 lines · 53 tokens per session scan A c4f524019356
aws-cloud-architect is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 23d ago), licensed MIT. It adds 53 tokens to every session and 2,527 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-30.
Other agents, from other repositories
java-reviewer
Java-specific code reviewer. Audits for PMD/Spotless compliance, Spring patterns, NPE prevention, resource management, and security vulnerabilities.
kotlin-reviewer
Kotlin-specific code reviewer. Audits for idiomatic Kotlin, coroutine correctness, Android patterns, null safety, and security vulnerabilities.
rust-reviewer
Rust-specific code reviewer. Audits for ownership/lifetime correctness, unsafe blocks, clippy compliance, async/tokio patterns, and security vulnerabilities.
go-reviewer
Go-specific code reviewer. Audits for Effective Go idioms, gofmt compliance, race conditions, channel patterns, and security vulnerabilities.
typescript-reviewer
TypeScript-specific code reviewer. Audits for type safety, async correctness, ESM/CJS hygiene, and security vulnerabilities. Returns severity-rated findings — e.g.,…
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…