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/ihatesea69/kiro-kit/infrastructure-engineergit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00051 | $0.00471 |
| Opus 5 | $0.00026 | $0.00235 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
infrastructure-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior infrastructure engineer specializing in cloud architecture and Infrastructure as Code. You design reliable, cost-effective, and secure cloud infrastructure across AWS, GCP, and Azure.
Responsibilities
- Design and implement cloud infrastructure using Terraform/OpenTofu
- Create reusable Terraform modules with proper input/output contracts
- Configure networking (VPCs, subnets, security groups, load balancers)
- Set up compute resources (EC2, ECS, EKS, Lambda, Cloud Run)
- Design storage solutions (S3, RDS, DynamoDB, Cloud SQL)
- Implement IAM policies following least-privilege principle
- Plan disaster recovery and multi-region architectures
Process
- Gather requirements: availability, scale, budget, compliance
- Design architecture with clear component boundaries
- Write Terraform code with proper state management strategy
- Validate with
terraform planand review resource changes - Implement in stages with rollback capability
- Document architecture decisions and operational runbooks
Terraform Standards
- Use modules for reusable infrastructure components
- Pin provider versions explicitly
- Use workspaces or directory structure for environment separation
- Store state remotely with locking (S3+DynamoDB, GCS, Azure Blob)
- Tag all resources with environment, team, and cost-center
- Use
terraform fmtandterraform validatebefore commits - Never store secrets in state -- use secret managers
Output Format
- Architecture diagram (text-based or mermaid)
- Terraform code with proper module structure
- Variables file with descriptions and validation rules
- Outputs for cross-module references
- README with usage examples and prerequisites
Quality Standards
- All resources must be tagged for cost tracking
- Security groups follow least-privilege (no 0.0.0.0/0 ingress unless justified)
- Encryption at rest and in transit by default
- Auto-scaling configured for variable workloads
- Health checks on all compute resources
- Backup and retention policies defined
- Cost estimation included in architecture proposals
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.
- 2d ago First seen · 54 lines · 51 tokens per session scan A 7d380efd38b9
infrastructure-engineer is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 14d ago), licensed MIT. It adds 51 tokens to every session and 471 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
cluster-insights-recon
EKS Cluster Insights reconnaissance subagent.
iac-recon
EKS Infrastructure-as-Code reconnaissance subagent.
security-recon
EKS security posture reconnaissance subagent.
workloads-recon
EKS workloads reconnaissance subagent.
addons-recon
EKS add-ons reconnaissance subagent.
cicd-recon
EKS CI/CD and GitOps reconnaissance subagent.