A set of guidance for Talos Linux nodes, a Kubernetes-focused operating system, including machine configuration, kernel settings, extensions, upgrades, reboots, and planned power work. It distinguishes staging configuration from actually upgrading a node.

Use it before editing Talos templates, changing versions or kernel settings, running node recipes, upgrading or rebooting nodes, or changing power plans.

It prevents stale templates from downgrading nodes and prevents changes that only appear applied because validation did not check live behavior. It also clarifies which command is needed for boot-image changes.

How Aviator-Coding/home-ops configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to Aviator-Coding/home-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Aviator-Coding/home-ops/main/.agents/skills/talos-nodes/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Aviator-Coding/home-ops

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aviator-coding/home-ops/talos-nodes/github.svg)](https://agentmods.dev/skills/aviator-coding/home-ops/talos-nodes)

Your own site

<a href="https://agentmods.dev/skills/aviator-coding/home-ops/talos-nodes"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/talos-nodes/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aviator-coding/home-ops/talos-nodes"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/talos-nodes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,623 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.

Model	Per session	Once invoked
Fable 5.1	$0.00096	$0.01623
Opus 5.5	$0.00038	$0.00649
Sonnet 5.5	$0.00019	$0.00325
Haiku 4.5	$0.00010	$0.00162

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

Security

Grade A, and why

talos-nodes 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 23d 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.

.agents/skills/talos-nodes/SKILL.md · 48 lines

How it starts

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

Talos nodes: machine config, upgrades and planned power work

Talos files are not applied by Flux. Merging a template change runs a schema-only CI check. An operator with a live talosconfig still has to apply or upgrade each node. talosctl validate does not catch bad enums, bad CIDRs, or a missing install disk.

Tripwires

apply-node is not upgrade-node. apply-node stages machine config. That is enough for machineconfig.yaml.j2 and nodes/*.yaml.j2. Kernel args and system extensions live in the Image Factory schematic, so schematic.yaml.j2 changes boot only via upgrade-node (talosctl upgrade -i <image> -m powercycle). An apply-only schematic edit does nothing.
The six image pins in machineconfig.yaml.j2 are a second copy of the tuppr versions. Installer, kubelet, apiserver, controller-manager, proxy, scheduler. A Renovate bump of the template does not upgrade the cluster. A tuppr upgrade does not edit the template. Applying a stale template downgrades a node. Before apply-node, match the template to kubectl get nodes -o wide and the tuppr CRs. scripts/ci/version-consistency.sh counts exactly six image pins: never put an image reference in a comment.
A merged bump of system-upgrade/tuppr/upgrades/talosupgrade.yaml is an unattended powercycle roll. tuppr consumes that CR directly (rebootMode: powercycle). Its healthChecks gate on VolSync ReplicationSource Synchronizing=False and CephCluster HEALTH_OK. They do not look at kopiur. With VolSync left on three claims, a kopiur-only failure does not block the roll. Treat that file like a live upgrade. Skill renovate.
Before any node reboot (upgrade-node, reboot-node, reset-node, or an OSD roll): ceph status is HEALTH_OK and task rook:check-osd-device-paths is clean. Rook #17224 bakes unstable /dev/nvmeXn1 names into OSD deployments. One node at a time, HEALTH_OK between nodes. osdMaxUpdatesInParallel is 1. Skill rook-ceph.
Never just talos shutdown-node for planned power work. The recipe hard-codes talosctl shutdown --force, which skips cordon and drain. Use plain talosctl shutdown. Runbook: power-down-up.md.
talos-3's Arc Pro B70 dock has its own PSU. A host powercycle does not cycle it (SLTCAP PowerController=0). pcie_port_pm=off in the schematic prevents the root port from runtime-suspending to D3hot; it is not retroactive and does not replace dock-PSU-first power-on. Runbook: talos-3-b70-reboot.md.
domains: [] must be explicit in the machine config. A nil domains list keeps the DHCP search domain. forwardKubeDNSToHost: true requires Cilium socketLB.hostNamespaceOnly. MGLRU is disabled via machine.sysfs (kernel/mm/lru_gen/enabled: "0"), not a kernel arg. The kube-system/mglru-disable DaemonSet re-asserts the same sysfs every 300s; do not delete either until a reboot proves the other holds. Skill system-namespaces.
features.kubernetesTalosAPIAccess.allowedKubernetesNamespaces includes system-upgrade and actions-runner-system. That allowlist is what lets tuppr (os:admin) and the runner (os:operator, the least role that can talosctl image pull) reach the Talos API. Moving tuppr out of system-upgrade needs apply-node on all three nodes first. Skill system-namespaces.
Node names, not the VIP. talos-1|talos-2|talos-3 are 10.10.10.11/12/13. Never target 10.10.10.10. Roll order for planned work is talos-3, then talos-2, then talos-1, unless the power-down runbook says otherwise (it shuts talos-3 down last).

Read the full file on GitHub · 48 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

23d ago Changed de0f4ecdd9f2
25d ago First seen · 48 lines · 96 tokens per session scan A 3a44f98da3b4

Subscribe to this mod's changes

talos-nodes is a skill published in the GitHub repository Aviator-Coding/home-ops (3 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,623 once invoked, about $0.0004 per session on Opus 5.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-29.

DevOps and cloud

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

home-ops: Skill for Claude Code