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 talosctlgit 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/talosctl)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/talosctl"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/talosctl.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.00033 | $0.08178 |
| Opus 5 | $0.00016 | $0.04089 |
| Sonnet 5 | $0.00007 | $0.01636 |
| Haiku 4.5 | $0.00003 | $0.00818 |
Grade A, and why
talosctl 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 8d 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 — 552 lines — stays where its author put it; the contents beside it link to each section on GitHub.
talosctl — CLI Operations
For machine config YAML (documents, patching) see talosconfig. For Terraform provider see talos-terraform.
⚠️ Configuration Changes Require Dry-Run + Verification
Every apply-config and patch machineconfig MUST be dry-run first, and the user MUST review/approve the output before anything is applied:
# Dry-run first — always
talosctl patch machineconfig --nodes <ip> --patch @patch.yaml --dry-run
talosctl apply-config --nodes <ip> --file config.yaml --dry-run
Only after the user explicitly confirms the dry-run output, run without --dry-run.
⚠️ apply-config Needs the FULL Config File
talosctl apply-config --file <config> replaces the node's entire machine configuration with the contents of <config>. It is NOT a patch tool — providing a partial YAML wipes all unspecified settings.
- Full-file changes (install, network rewrite, secrets rotation) →
talosctl apply-config --file <full-config.yaml> - Targeted changes (one field) →
talosctl patch machineconfig --patch @patch.yaml - Get the current full config first:
talosctl get machineconfig v1alpha1 -o yaml
CLI Quick Reference
Cluster Lifecycle
| Command | Purpose |
|---|---|
talosctl gen config <name> <endpoint> --with-secrets secrets.yaml |
Generate cluster configs (full config files) |
talosctl gen secrets --output-file secrets.yaml |
Generate secrets bundle |
talosctl apply-config --nodes <ip> --file config.yaml --insecure |
Apply FULL config to new node |
talosctl bootstrap --nodes <ip> |
Bootstrap etcd (once, first CP only) |
talosctl kubeconfig --nodes <ip> --force |
Get admin kubeconfig (overwrite existing) |
talosctl health --nodes <cps> --wait-timeout=10m |
Check cluster health |
talosctl version |
Show client + server versions |
Maintenance
| Command | Purpose |
|---|---|
talosctl upgrade --image ghcr.io/siderolabs/installer:v1.13.8 --reboot-mode=default |
Upgrade Talos OS (drains node by default) |
talosctl upgrade --no-reboot |
Upgrade, defer reboot (replaces deprecated --stage) |
talosctl upgrade --drain=false |
Upgrade without draining (use with care) |
talosctl upgrade-k8s --to v1.36.2 --dry-run |
Upgrade Kubernetes (dry-run first) |
talosctl upgrade-k8s --to v1.36.2 |
Upgrade Kubernetes |
talosctl rollback --nodes <ip> |
Rollback Talos to previous install |
talosctl reboot --mode=default |
Reboot node (default/force/powercycle) |
talosctl reset --graceful --reboot |
Reset node (removes from cluster) |
talosctl shutdown |
Shutdown node (cordon/drain first, --force to skip) |
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.
- 8d ago First seen · 552 lines · 33 tokens per session scan A 85411bfd9fc7
talosctl is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 24d ago), licensed MIT. It adds 33 tokens to every session and 8,178 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.