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.
npx skills add Aidas-dev/k8s-agent-skills --skill talos-terraformgit clone --depth 1 https://github.com/Aidas-dev/k8s-agent-skillsWrote 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/aidas-dev/k8s-agent-skills/talos-terraform)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/talos-terraform"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/talos-terraform/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/skills/aidas-dev/k8s-agent-skills/talos-terraform"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/talos-terraform.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.00050 | $0.02026 |
| Opus 5 | $0.00025 | $0.01013 |
| Sonnet 5 | $0.00010 | $0.00405 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade C, and why
talos-terraform scanned grade C with 1 finding 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 10d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
- **Regenerating secrets on an existing cluster** — `talos_machine_secrets` is bootstrap-only. On a live cluster, extract secrets from the cluster and store gitignored. Regenerating rotates all certs → outage. How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
talos-terraform — Terraform Provider
For CLI operations see talosctl. For machine config YAML see talosconfig.
Provider: siderolabs/talos
Latest stable: v0.11.0 (2026-04-27) — SDK targets Talos v1.13 config line
Next (alpha): v0.12.0-alpha.x (2026-06-25) — adds talos_machine/talos_cluster, based on Talos v1.14. NOT stable.
Provider Setup
terraform {
required_providers {
talos = {
source = "siderolabs/talos"
version = "~> 0.11.0" # stable
}
}
}
Sidero-Blessed Production Pattern
Production-proven pattern for managing an EXISTING Talos cluster with Terraform. Core idea: generate config from live cluster secrets + patch files, apply with the stable talos_machine_configuration_apply resource, and let a separate system own OS/K8s upgrades.
Why NOT talos_machine (alpha)
talos_machine exists only in v0.12.0-alpha. It has a Create/Update bug with image = null — Optional+Computed fields plan as Unknown, and the provider attempts an upgrade with an empty image ref. If OS upgrades are owned elsewhere (e.g. tuppr TalosUpgrade CRs), avoid talos_machine entirely.
Architecture
locals (node map + live secrets + talosconfig)
→ data talos_machine_configuration (per node: live secrets + patch file)
→ resource talos_machine_configuration_apply (apply config to node)
→ apply_mode = staged_if_needing_reboot
→ lifecycle prevent_destroy
The Pattern
# 1. Cluster secrets from the LIVE cluster — NEVER regenerate.
# Regenerating rotates all certs. Extracted once, gitignored.
locals {
cluster_secrets = jsondecode(file("${path.module}/local_cluster_secrets.json"))
}
# 2. Client config from the cluster's talosconfig (os:admin).
# certs.os = machine CA (for config gen) — NOT a valid apid client.
# apid RBAC requires subject O=os:admin.
locals {
talos_cfg = yamldecode(file("${path.module}/talosconfig.yaml"))
talos_client_config = {
ca_certificate = local.talos_cfg.contexts[local.talos_cfg.context].ca
client_certificate = local.talos_cfg.contexts[local.talos_cfg.context].crt
client_key = local.talos_cfg.contexts[local.talos_cfg.context].key
}
}
# 3. Generate machine config per node: live secrets + version contract +
# the applied config as patch (byte-exact reproduction of node state).
data "talos_machine_configuration" "node" {
for_each = local.nodes
cluster_name = var.cluster_name
cluster_endpoint = each.value.endpoint
machine_type = each.value.role # controlplane | worker
machine_secrets = local.cluster_secrets
kubernetes_version = each.value.kubernetes_version
talos_version = each.value.talos_version # RECOMMENDED: pin it
config_patches = [file("${path.module}/patches/${each.key}-apply.yaml")]
}
# 4. Apply config — config-only, no OS version sync.
resource "talos_machine_configuration_apply" "node" {
for_each = local.nodes
node = each.value.ip
client_configuration = local.talos_client_config
machine_configuration_input = data.talos_machine_configuration.node[each.key].machine_configuration
apply_mode = "staged_if_needing_reboot"
lifecycle {
prevent_destroy = true # live nodes: reconcile config only, never recreate
}
}
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.
- 10d ago First seen · 168 lines · 50 tokens per session scan C b45fe1298d5d
talos-terraform is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 27d ago), licensed MIT. It adds 50 tokens to every session and 2,026 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
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".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…