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 tupprgit 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/tuppr)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/tuppr"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tuppr/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/tuppr"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tuppr.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.00062 | $0.01749 |
| Opus 5 | $0.00031 | $0.00874 |
| Sonnet 5 | $0.00012 | $0.00350 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
tuppr 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tuppr — Talos & Kubernetes Upgrade Controller
Automated, GitOps-friendly upgrades of Talos Linux and Kubernetes. Declare a target version in a custom resource; tuppr plans and executes the rollout — draining, upgrading, rebooting, and health-checking each node (sequentially or in parallel batches). Upgrades always run from a healthy node — tuppr never self-upgrades the node it runs on.
Repo: github.com/home-operations/tuppr
API group: tuppr.home-operations.com/v1alpha1
Latest chart: 0.5.0 (OCI ghcr.io/home-operations/charts/tuppr)
Docs: tuppr.home-operations.com
When to Use tuppr
- You want Talos/K8s upgrades driven by the Kubernetes API (GitOps) instead of running
talosctl upgradeby hand - You manage nodes with Terraform but want upgrades owned separately (see
talos-terraform— tuppr is the "dedicated upgrade system" that pattern assumes)
For manual upgrades → talosctl. For machine config → talosconfig. This skill is only the controller.
Install
# Direct
helm install tuppr oci://ghcr.io/home-operations/charts/tuppr \
--version 0.5.0 \
--namespace system-upgrade --create-namespace
GitOps (Flux) — the recommended production path:
apiVersion: source.toolkit.fluxcd.io/v1
kind: OCIRepository
metadata:
name: tuppr
namespace: system-upgrade
spec:
interval: 15m
url: oci://ghcr.io/home-operations/charts/tuppr
layerSelector:
mediaType: application/vnd.cncf.helm.chart.content.v1.tar+gzip
operation: copy
ref:
tag: 0.5.0
---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: tuppr
namespace: system-upgrade
spec:
chartRef:
kind: OCIRepository
name: tuppr
interval: 1h
values:
replicaCount: 2
monitoring:
serviceMonitor:
enabled: true
Prerequisites
- The Talos API-access CRD (a real Talos cluster)
talosServiceAccount.create: true(default) — makes Talos generate the*-talosconfigSecret the controller mounts. On non-Talos clusters (e2e/kind), set false and provide the Secret yourself- Leader election recommended (default enabled; only one controller active)
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 · 187 lines · 62 tokens per session scan A eb8779ae2bcd
tuppr is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 62 tokens to every session and 1,749 once invoked, about $0.0003 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
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
nextjs-deployment
Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output…
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
devops-automator
Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use…