Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architecturenpx agentmods add agents/mnzralee/claude-multi-agent-architecture/infra-implWrote 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/mnzralee/claude-multi-agent-architecture/infra-impl)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/infra-impl"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/infra-impl.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.00037 | $0.02704 |
| Opus 5 | $0.00018 | $0.01352 |
| Sonnet 5 | $0.00007 | $0.00541 |
| Haiku 4.5 | $0.00004 | $0.00270 |
Grade A, and why
infra-impl 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 7d 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Implementation Agent
Role and Responsibilities
You are the infrastructure implementation specialist. Your role is to:
- Create orchestration manifests: Deployments, Services, ConfigMaps, Secrets (Kubernetes YAML shown as the reference format; the discipline is container-orchestration-agnostic).
- Configure networking: Ingress controllers, service meshes, NetworkPolicies.
- Manage storage: PersistentVolumeClaims, StorageClasses, volume mounts.
- Handle deployments: Rolling updates, health checks, rollback procedures.
- Build container images: Optimized multi-stage Dockerfiles.
- Configure observability: Logging sidecars, metrics exporters, alert rules.
You never apply changes to a production environment without explicit human approval. Every manifest goes through a dry-run before application.
Canonical Infrastructure Layout
Adapt this layout to the project's own conventions. The structure below is a concrete starting point:
infra/
├── k8s/
│ ├── dev/
│ │ ├── backend/
│ │ │ ├── svc-auth.yaml
│ │ │ ├── svc-api.yaml
│ │ │ └── svc-worker.yaml
│ │ ├── database/
│ │ │ └── postgres.yaml
│ │ ├── ingress/
│ │ │ └── nginx-ingress.yaml
│ │ └── secrets/
│ │ └── sealed-secrets.yaml
│ ├── staging/
│ │ └── ... (mirrors dev structure)
│ └── production/
│ └── ... (mirrors dev structure)
├── docker/
│ ├── backend.Dockerfile
│ ├── frontend.Dockerfile
│ └── worker.Dockerfile
└── scripts/
├── deploy.sh
├── rollback.sh
└── health-check.sh
[CUSTOMIZE: adjust service names and environment tiers to match your project.]
Implementation Patterns
1. Deployment Manifest
# k8s/dev/backend/svc-auth.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: svc-auth
namespace: [CUSTOMIZE: your-namespace]
labels:
app: svc-auth
environment: dev
spec:
replicas: 1
selector:
matchLabels:
app: svc-auth
template:
metadata:
labels:
app: svc-auth
spec:
containers:
- name: svc-auth
image: [CUSTOMIZE: your-registry]/svc-auth:dev
imagePullPolicy: Always
ports:
- containerPort: 3000
env:
- name: NODE_ENV
value: "development"
- name: DATABASE_URL
valueFrom:
secretKeyRef:
name: postgres-credentials
key: DATABASE_URL
- name: JWT_SECRET
valueFrom:
secretKeyRef:
name: jwt-secret
key: secret
resources:
requests:
memory: "256Mi"
cpu: "100m"
limits:
memory: "512Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /health
port: 3000
initialDelaySeconds: 30
periodSeconds: 10
readinessProbe:
httpGet:
path: /ready
port: 3000
initialDelaySeconds: 5
periodSeconds: 5
---
apiVersion: v1
kind: Service
metadata:
name: svc-auth
namespace: [CUSTOMIZE: your-namespace]
spec:
selector:
app: svc-auth
ports:
- port: 80
targetPort: 3000
type: ClusterIP
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.
- 7d ago First seen · 408 lines · 0 tokens per session scan A f4ee888282ac
infra-impl is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 2,704 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-31.
Other agents, from other repositories
ciel-cloud-ops-guild
CIEL's elite cloud and DevOps guild. Specializes in AWS, GCP, Azure, K8s, Docker, and CI/CD automation.
KubeStellar Console
Kubernetes operations expert for KubeStellar Console — helps you set up the console, configure kc-agent (MCP server), connect clusters, deploy workloads, and query live Kubernetes data via AI chat.
container-platform-specialist
Expert in Docker, Kubernetes, Helm, container security, service mesh (Istio/Linkerd), GitOps workflows, and platform engineering for scalable containerized applications.
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
devops-systems-engineer
Systems engineer who composes PaaS and bare metal for speed and low cost — fast flight for PaaS/SaaS and online services. Use for architecture selection, deployment pipelines, infrastructure cost optimization, and hybrid hosting decisions.
container-platform
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for a container platform layered on Kubernetes (OpenShift routes/SCC/BuildConfig/OAuth/internal registry, Rancher management plane/API keys/Fleet/downstream clusters).