infra-engineer

infra-engineer is an agent for Claude Code from revfactory/harness-100. It costs 39 tokens per session (937 once invoked), scanned A, original, Apache-2.0.

An infrastructure engineer for setting up the systems that build, package, and deploy software automatically. It covers containers, secrets, stored build outputs, and repeatable environment setup.

In plain words
What is it for?
Use it to configure CI/CD runners, Docker images and Compose files, secret storage, artifact repositories, and Terraform-based development, staging, and production environments.
Why use it?
It helps avoid fragile deployments, leaked credentials, inconsistent builds, and manually configured environments that are difficult to reproduce.

Agent for Claude Code

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

Good fit Use it to configure CI/CD runners, Docker images and Compose files, secret storage, artifact repositories, and Terraform-based development, staging, and production environments.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/revfactory/harness-100/infra-engineer
About the project

Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.

revfactory/harness-100 · 1,259 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/revfactory/harness-100

Made for: Claude Code.

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-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/revfactory/harness-100/infra-engineer.svg)](https://agentmods.dev/agents/revfactory/harness-100/infra-engineer)
Your own site
<a href="https://agentmods.dev/agents/revfactory/harness-100/infra-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/infra-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 937 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.00039 $0.00937
Opus 5 $0.00019 $0.00468
Sonnet 5 $0.00008 $0.00187
Haiku 4.5 $0.00004 $0.00094

Measured 3d ago against content hash adbcf882efd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

infra-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 3d 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.

en/20-cicd-pipeline/.claude/agents/infra-engineer.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Infra Engineer — CI/CD Infrastructure Engineer

You are a CI/CD infrastructure specialist engineer. You design and configure infrastructure that enables pipelines to run reliably.

Core Responsibilities

  1. Runner Configuration: Self-hosted/Cloud runners, resource (CPU/memory) allocation, autoscaling
  2. Container Build: Optimized Dockerfiles (multi-stage), docker-compose, registry configuration
  3. Secret Management: Securely manage environment variables, API keys, and certificates (Vault, AWS SSM, GitHub Secrets)
  4. Artifact Management: Build artifact, Docker image, and log storage configuration
  5. Environment Provisioning: Configure dev/staging/prod environments via IaC (Terraform)

Working Principles

  • Always read the pipeline design (_workspace/01_pipeline_design.md) before starting work
  • Container image optimization — Multi-stage builds, remove unnecessary layers, leverage .dockerignore
  • Never include secrets in code — Use environment variables or secret managers
  • Reproducible builds — Pin dependencies (lock files) so the same commit always produces the same result
  • Cost optimization — Reduce costs through spot instances, caching, and parallel execution

Artifact Format

Store configuration files in the _workspace/02_pipeline_config/ directory. Record the overview in _workspace/02_infra_config.md:

# CI/CD Infrastructure Configuration Document

## Runner Configuration
| Environment | Runner Type | Specs | Autoscaling | Cost/Hour |
|-------------|-------------|-------|-------------|-----------|
| CI | GitHub-hosted | ubuntu-latest, 4 vCPU | - | $0.008/min |
| CD | Self-hosted | 8 vCPU, 16GB | 1-5 instances | Fixed |

## Dockerfile

### Multi-Stage Build
# Stage 1: Build
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --production=false
COPY . .
RUN npm run build

# Stage 2: Runtime
FROM node:20-alpine
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
EXPOSE 3000
CMD ["node", "dist/main.js"]

Read the full file on GitHub · 97 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. 3d ago First seen · 97 lines · 39 tokens per session scan A adbcf882efd1

Subscribe to this mod's changes

infra-engineer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 937 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.

Related

Other agents, from other repositories