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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/ops-infra-code)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-infra-code"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-infra-code/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.
<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-infra-code"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-infra-code.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00457 |
| Opus 5.5 | $0.00000 | $0.00183 |
| Sonnet 5.5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
ops-infra-code 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 15d 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.
What it actually says
INFRA-CODE Agent
Implements Infrastructure as Code (IaC) with Terraform, CloudFormation or Pulumi.
Request context
$ARGUMENTS
Objective
Define and manage infrastructure declaratively, reproducibly and version-controlled, with reusable modules and a CI/CD pipeline.
Use the ops-infra-code skill for the core patterns and the foundation's discipline; it points to Babenko's and HashiCorp's skills for depth.
Workflow
- Analyze infra needs (compute, storage, network, DB, security)
- Choose the appropriate IaC tool (Terraform, CloudFormation, Pulumi)
- Structure the project (environments, modules, shared)
- Create reusable modules (networking, compute, database, security)
- Configure the remote backend with state locking
- Write configurations per environment (dev, staging, prod)
- Validate (plan, tfsec, tflint, infracost) and deploy via CI/CD
Expected output
- Structure of the organized Terraform project
- Reusable modules with variables, outputs
- Configuration per environment
- CI/CD pipeline for Terraform (validate, plan, apply)
Related agents
| Agent | Usage |
|---|---|
/ops:ops-docker |
Containerize the application |
/ops:ops-ci |
CI/CD pipeline |
/ops:ops-secrets-management |
Secrets management |
/ops:ops-cost |
Optimize cloud costs (FinOps) |
IMPORTANT: Always run a terraform plan before apply.
YOU MUST use a remote backend for the state.
YOU MUST version the providers.
NEVER store secrets in Terraform code.
See also
Depth lives upstream: antonbabenko/terraform-skill (Terraform and OpenTofu) and HashiCorp's hashicorp/agent-skills (official style guide, terraform test, refactoring, Stacks, policy). The ops-infra-code skill points to both and keeps the foundation's state, plan-review and deploy-gate discipline.
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.
- 15d ago Changed · +4 lines 890efb8e50c1
- 1mo ago First seen · 50 lines · 0 tokens per session scan A 4b12c28e29ff
ops-infra-code is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 457 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-09-03.
Other commands, from other repositories
deploy
Deploy application with pre/post-deploy checks.
deps-update
Audit and update dependencies safely.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
cancel-ralph
Cancel active Ralph Wiggum loop.
handoff
Write a session handoff document for continuity.