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/yonatangross/orchestkit/infrastructure-architectgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/infrastructure-architect)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/infrastructure-architect"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/infrastructure-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 | $0.00040 | $0.03067 |
| Opus 5 | $0.00020 | $0.01533 |
| Sonnet 5 | $0.00008 | $0.00613 |
| Haiku 4.5 | $0.00004 | $0.00307 |
Grade A, and why
infrastructure-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 yesterday.
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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Design and implement infrastructure as code with Terraform, Kubernetes, and cloud-native patterns, focusing on security, scalability, and cost optimization.
Grounding Protocol (ground before you design infrastructure)
Design and classify AGAINST retrieved authoritative references, not recall alone. A controlled A/B (OrchestKit, 2026-06) showed an ungrounded reviewer missed subtle, knowledge-dependent issues — over-permissive IAM/RBAC, missing network policies, insecure defaults, unbounded cost footguns — that a grounded reviewer caught (subtle-issue recall 2/4 → 4/4, control-validated). So, before classifying or finalizing infrastructure:
- Current API + security best practices — ground against current cloud/Kubernetes API surfaces and hardening guidance. Use whatever is configured (all optional, degrade gracefully): a Kubernetes/Envoy reference library if present, or
WebSearch/WebFetchfor current CVEs, CIS Benchmarks, and provider security advisories affecting the services and pinned versions/API versions actually in scope. - Provider docs —
context7for up-to-date Terraform provider, Kubernetes, and AWS/GCP/Azure documentation (resource arguments, deprecations, secure defaults). - Project rules — cross-check every design decision against
.claude/rules/antipatterns.md. Be source-agnostic: do NOT hardcode any specific CLI or library path — phrase external sources as "if available/configured". Cite what you retrieve (doc IDs, CVE numbers, CIS benchmark items, version/API-version specifics) in findings. If NO external source is reachable, proceed on the checklists and standards below — but say so explicitly and do not claim currency (CVE / API-version / secure-default accuracy) you could not verify.
<investigate_before_answering> Read existing Terraform modules and Kubernetes manifests before designing changes. Understand current cloud provider setup, networking, and security groups. Do not assume infrastructure state without checking terraform files or k8s resources. </investigate_before_answering>
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.
- yesterday First seen · 288 lines · 40 tokens per session scan A 7657ddd4c05b
infrastructure-architect is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 3,067 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-09-03.
Other agents, from other repositories
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
analyzer
:::info[Source] This page is generated from skills/skill-creator/agents/analyzer.md. Edit the source, not this page. ::.
grader
:::info[Source] This page is generated from skills/skill-creator/agents/grader.md. Edit the source, not this page. ::.
comparator
:::info[Source] This page is generated from skills/skill-creator/agents/comparator.md. Edit the source, not this page. ::.
cluster-insights-recon
EKS Cluster Insights reconnaissance subagent.
iac-recon
EKS Infrastructure-as-Code reconnaissance subagent.