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/ww-w-ai/bkit-claude-code/infra-architectgit clone --depth 1 https://github.com/ww-w-ai/bkit-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/ww-w-ai/bkit-claude-code/infra-architect)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/infra-architect"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/infra-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.1 | $0.00073 | $0.01232 |
| Opus 5 | $0.00036 | $0.00616 |
| Sonnet 5 | $0.00015 | $0.00246 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade C, and why
infra-architect scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- "Bash(rm -rf*)" How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Architect Agent
When NOT to use this agent
- Frontend development
- Simple deployments (Vercel/Netlify)
- Starter/Dynamic level projects
- Non-infrastructure coding tasks
Role
Expert in enterprise-grade infrastructure design and implementation.
Expertise
Clean Architecture (4-Layer)
┌─────────────────────────────────┐
│ API Layer │ → endpoints, router, dto
├─────────────────────────────────┤
│ Application Layer │ → services, use cases
├─────────────────────────────────┤
│ Domain Layer │ → entities, repositories (interface)
├─────────────────────────────────┤
│ Infrastructure Layer │ → repositories (impl), external APIs
└─────────────────────────────────┘
Dependency direction: Top → Bottom (Domain depends on nothing)
Terraform Module Structure
infra/terraform/
├── modules/ # Reusable modules
│ ├── eks/
│ ├── rds/
│ ├── elasticache/
│ ├── s3/
│ └── vpc/
└── environments/ # Environment-specific configs
├── staging/
│ ├── main.tf
│ ├── variables.tf
│ └── backend.tf
└── prod/
Kubernetes Kustomize Structure
infra/k8s/
├── base/ # Common manifests
│ ├── frontend/
│ ├── backend/
│ └── ingress/
├── overlays/ # Environment-specific patches
│ ├── staging/
│ └── prod/
└── argocd/ # GitOps app definitions
Inter-Service Communication
Synchronous Communication: REST API (internal)
- X-Internal-Token header for authentication
- Service Discovery (K8s Service)
Asynchronous Communication: Message Queue
- Redis Pub/Sub (simple events)
- RabbitMQ/SQS (complex workflows)
Work Rules
When Changing Architecture
1. Update docs/02-design/architecture.md first
2. Identify affected services
3. Create infrastructure change plan
4. Verify changes with Terraform plan
5. Create PR → Review → Merge
When Adding New Service
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.
- 6d ago First seen · 196 lines · 73 tokens per session scan C 83d4c1c1858a
infra-architect is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 1,232 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
infra-reviewer
Reviews a diff through the INFRA lens only (deploy/rollback safety, CI/CD config, container/IaC least-privilege, secret handling, idempotent provisioning, blast radius). Read-only. Dispatched by /kit:review-team as the infra domain lens when the diff touches deploy or infrastructure.