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/atretyak1985/swarmerynpx agentmods add skills/atretyak1985/swarmery/infrastructure-as-codeWrote 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/skills/atretyak1985/swarmery/infrastructure-as-code)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/infrastructure-as-code"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/infrastructure-as-code.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.00078 | $0.03778 |
| Opus 5 | $0.00039 | $0.01889 |
| Sonnet 5 | $0.00016 | $0.00756 |
| Haiku 4.5 | $0.00008 | $0.00378 |
Grade A, and why
infrastructure-as-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 4d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Enforce the invariant that a fresh server deploy of the project must succeed from code alone, without any manual kubectl patch, kubectl exec, or helm --set overrides that are not persisted. Covers config drift detection, the populated values pattern, post-incident IaC capture, and the "Where Changes Go" decision map.
When to use this skill (triggers)
- Deploying the platform to a new server or environment and verifying all config is in code
- Auditing config drift after manual cluster fixes (kubectl patch, psql exec, gcloud console changes)
- Preparing or regenerating
.populated.yamlvalues files via the infrastructure repo'smapEnvValuesFromEnv.sh(or equivalent env-mapping script) - Verifying that all manual cluster changes are captured in the correct source file (Helm values, Terraform, migration script)
- Diagnosing literal
$VARIABLE_NAMEstrings appearing in K8s Secrets
When NOT to use this skill (anti-triggers)
- Writing or debugging Helm chart templates -- use
helm-chart-expert - Checking migration safety or schema alignment -- use
migration-check - Deploying the edge service (project.json → device) to edge devices or managing k3s -- use
kubernetes-deployment - Managing Keycloak realm/client configuration -- use
keycloak
Required environment (Runtime: .claude/skills/infrastructure-as-code/SKILL.md)
- Tools/libraries:
helm(v3.10+),kubectl,terraform,diff,bash - Scripts: the infrastructure repo's
files/mapEnvValuesFromEnv.shandfiles/runDatabaseMigrations.sh(or the project's equivalents) - Repos: the infrastructure, chart, and Terraform repos (project.json → repos)
Terraform environment layout (canonical reference)
Canonical doc: the Terraform repo's README §Environment layout. Read it before adding any new resource; it is the single source of truth for current vs legacy env dirs.
Common patterns to watch for:
| Element | Pattern |
|---|---|
| Active env dirs | the currently maintained environments/<org>/{shared,dev,...} tree |
| Legacy (DEAD) env dirs | superseded environments/... trees whose backend state buckets no longer exist -- do not add resources there |
| GCS state bucket | often a single bucket, with per-env discrimination via prefix = "iac/env-<name>" |
| Terraform runner GCP project | may differ from the cluster's GCP project -- trust the repo README, not stale variable defaults |
| Environment naming | the staging alias (project.json → cloud.envAlias) may appear as dev in Terraform paths -- same environment |
| Cutover history | look for cutover notes committed alongside the env dirs |
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.
- 4d ago First seen · 294 lines · 78 tokens per session scan A 7e56a65034eb
infrastructure-as-code is a skill published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 3,778 once invoked, about $0.0004 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.
Other skills, from other repositories
tailscale
This skill should be used when managing Tailscale mesh VPN networks. Use when the user asks to "check tailscale status", "list tailscale devices", "ping a device", "send file via tailscale", "tailscale funnel", "tailscale serve", "create auth key", "check who's online", "tailscale exit node", "Magic DNS", or mentions…
gws-script
Apps Script: Deploy and manage Google Apps Script projects with gws script +push.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
azure-resource-manager-durabletask-dotnet
Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: "Durable Task Scheduler", "create scheduler", "task hub", "DurableTaskSchedulerResource", "provision…
azure-eventhub-dotnet
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming"…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".