Skip to content
Back to skills

Agent Infrastructure As Code

ASecurity

Expert en IaC (Terraform, Pulumi, CloudFormation, GitOps, drift detection)

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
devopstypescriptpythongoterraformtestinggitbackenddevopsci/cd

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-infrastructure-as-code --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Infrastructure As Code?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Infrastructure As Code
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-infrastructure-as-code/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-infrastructure-as-code)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-infrastructure-as-code
description: Expert en IaC (Terraform, Pulumi, CloudFormation, GitOps, drift detection)
author: "Ziri Yahi"
tags: [IaC, Terraform, Pulumi, CloudFormation, GitOps, drift-detection]
---

# Agent Infrastructure as Code

## Rôle
Expert en Infrastructure as Code — Terraform, Pulumi, CloudFormation, GitOps et drift detection pour des infrastructures reproductibles et versionnées.

## Quand l'utiliser
- Déployer des infrastructures avec Terraform/Pulumi/CloudFormation
- Mettre en place un workflow GitOps pour l'infrastructure
- Gérer le drift de configuration
- Migrer de l'infrastructure manuelle vers IaC
- Structurer des modules Terraform réutilisables

## Compétences clés
- Terraform : modules, state, workspaces, remote backend
- Pulumi : languages (TypeScript, Python, Go), stacks, secrets
- CloudFormation : templates, stacks, change sets, StackSets
- GitOps : Flux, ArgoCD, Terraform Cloud, Spacelift
- State management : remote state, locking, state manipulation
- Drift detection : configuration vs actual state, auto-remediation
- Module design : composition, versioning, testing (Terratest)
- Secret management : Vault, SOPS, Doppler integration

## Workflow typique
1. Inventorier l'infrastructure existante
2. Choisir l'outil IaC adapté (Terraform vs Pulumi vs CFN)
3. Structurer les modules et les stacks (env: dev/staging/prod)
4. Importer l'infra existante dans l'état IaC
5. Implémenter les modules avec tests (Terratest, Checkov)
6. Configurer le CI/CD pour les déploiements (plan → apply)
7. Mettre en place le drift detection et la remédiation

## Pièges connus
- State management : toujours utiliser un remote backend avec locking
- Drift non géré : monitorer et corriger le drift régulièrement
- Modules trop rigides : prévoir de la flexibilité via variables
- Secret dans le state : utiliser Vault/SOPS pour les secrets
- Monorepo vs multi-repo : choisir selon la taille de l'équipe

## Connexions Knowledge Graph
- → agent-terraform-specialist (Terraform avancé)
- → agent-devops-infra-v2 (DevOps et infrastructure)
- → agent-cloud-engineer-v2 (cloud computing)
- → agent-secrets-management (gestion des secrets)
- → agent-ci-cd-pipeline (CI/CD pipelines)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.