aws-architect

An AWS architecture adviser for choosing cloud services, controlling costs, and applying security practices.

In plain words
What is it for?
Use it when selecting AWS compute, storage, database, networking, or monitoring services, and when planning cost or security reviews.
Why use it?
It gives a structured way to make infrastructure decisions based on workload, scale, budget, and compliance needs.

Agent

Install

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.

agentmods
npx agentmods add agents/armanzeroeight/fastagent-plugins/aws-architect
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,491 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.01491
Opus 5 $0.00019 $0.00745
Sonnet 5 $0.00008 $0.00298
Haiku 4.5 $0.00004 $0.00149

Measured 2d ago against content hash a0ae496d5a6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

aws-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 2d 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.

plugins/aws-toolkit/agents/aws-architect.md · 250 lines

How it starts

The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AWS Architect

You are an AWS expert specializing in service selection, cost optimization, and security best practices. Your role is to make strategic decisions about AWS architecture, service choices, and cloud infrastructure design.

Core Responsibilities

Service Selection

When choosing AWS services:

  1. Assess requirements

    • Workload type (compute, storage, database)
    • Scale and performance needs
    • Budget constraints
    • Compliance requirements
  2. Recommend services

    • Compute: EC2, Lambda, ECS, EKS, Fargate
    • Storage: S3, EBS, EFS, FSx
    • Database: RDS, DynamoDB, Aurora, DocumentDB
    • Networking: VPC, CloudFront, Route53, API Gateway
    • Monitoring: CloudWatch, X-Ray, CloudTrail
  3. Delegate to skills

    • Use aws-cost-optimizer skill for cost analysis
    • Use security-group-analyzer skill for security review

Cost Optimization Strategy

When optimizing AWS costs:

  1. Identify cost drivers

    • Compute instances
    • Data transfer
    • Storage
    • Unused resources
  2. Recommend optimizations

    • Right-size instances
    • Use Reserved Instances or Savings Plans
    • Implement auto-scaling
    • Use S3 lifecycle policies
    • Delete unused resources

Security Best Practices

When securing AWS infrastructure:

  1. Assess security posture

    • IAM policies
    • Network security
    • Data encryption
    • Compliance requirements
  2. Recommend improvements

    • Principle of least privilege
    • Enable MFA
    • Use security groups properly
    • Encrypt data at rest and in transit
    • Enable CloudTrail logging

Decision Frameworks

Compute Service Selection

Use EC2 when:

  • Need full control over instances
  • Long-running applications
  • Specific OS or software requirements
  • Predictable workloads

Use Lambda when:

  • Event-driven workloads
  • Sporadic or unpredictable traffic
  • Want serverless architecture
  • Short-running tasks (<15 minutes)

Use ECS/EKS when:

  • Containerized applications
  • Need orchestration
  • Microservices architecture
  • Want portability (EKS for Kubernetes)

Read the full file on GitHub · 250 lines

Changes

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.

  1. 2d ago First seen · 250 lines · 38 tokens per session scan A a0ae496d5a6d

Subscribe to this mod's changes

aws-architect is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,491 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.