infra-impl

infra-impl is an agent for Claude Code from mnzralee/claude-multi-agent-architecture. It costs 0 tokens per session (2,704 once invoked), scanned A, original, MIT.

An infrastructure implementation agent for containers, deployment configuration, networking, storage, health checks, and observability.

In plain words
What is it for?
Use it to create container files and orchestration manifests, configure services and network policies, manage storage and secrets, set up health checks, and plan rollbacks.
Why use it?
It organizes deployment work and requires a dry run before changes are applied. Production changes still require explicit human approval.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is COPY apps/svc-auth ./apps/svc-auth.

Part of the claude-multi-agent-architecture plugin — 19 skills, 19 agents, 3 hooks shipped together

Good fit Use it to create container files and orchestration manifests, configure services and network policies, manage storage and secrets, set up health checks, and plan rollbacks.

Compare 6 agents from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architecture
agentmods
npx agentmods add agents/mnzralee/claude-multi-agent-architecture/infra-impl

Made for: Claude Code.

Or install claude-multi-agent-architecture, the plugin that ships this one along with the rest of its 19 skills, 19 agents, 3 hooks.

Wrote 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.

agentmods badge for infra-impl

README.md
[![agentmods](https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/infra-impl/github.svg)](https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/infra-impl)
Your own site
<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for infra-impl

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.02704
Opus 5.5 $0.00000 $0.01082
Sonnet 5.5 $0.00000 $0.00541
Haiku 4.5 $0.00000 $0.00270

Measured 2mo ago against content hash f4ee888282ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/agents/infra-impl.md · 408 lines

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:

  1. Create orchestration manifests: Deployments, Services, ConfigMaps, Secrets (Kubernetes YAML shown as the reference format; the discipline is container-orchestration-agnostic).
  2. Configure networking: Ingress controllers, service meshes, NetworkPolicies.
  3. Manage storage: PersistentVolumeClaims, StorageClasses, volume mounts.
  4. Handle deployments: Rolling updates, health checks, rollback procedures.
  5. Build container images: Optimized multi-stage Dockerfiles.
  6. 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

Read the full file on GitHub · 408 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. 2mo ago First seen · 408 lines · 0 tokens per session scan A f4ee888282ac

Subscribe to this mod's changes

infra-impl is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,704 tokens. 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.

Related

infra-impl compared with agents from other repositories

infra-impl next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
infra-implmnzralee/claude-multi-agent-architectureAgent81mo agoMITA0Claude Code
ciel-cloud-ops-guildjxoesneon/CielAgent17d agoApache-2.0A39Claude Code
KubeStellar Consolearchubbuck/workspace-architectAgent192d agoISCC47Claude Code
cloud-agentTyrusRC/praetorAgent8yesterdayApache-2.0A53Claude Code
FAI Kubernetes Expertfrootai/frootaiAgent74d agoMITA42Claude Code
integration-engineerrevfactory/harness-100Agent1.3k7mo agoApache-2.0A38Claude Code
vulnerability-scannerrevfactory/harness-100Agent1.3k7mo agoApache-2.0A29Claude Code