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 tekton-operatorgit 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/tekton-operator)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/tekton-operator"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton-operator/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/tekton-operator"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton-operator.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.00064 | $0.01892 |
| Opus 5 | $0.00032 | $0.00946 |
| Sonnet 5 | $0.00013 | $0.00378 |
| Haiku 4.5 | $0.00006 | $0.00189 |
Grade A, and why
tekton-operator 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 9d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tekton-operator — Install & Manage Tekton
For authoring pipelines see tekton-pipelines. For Pipelines-as-Code see tekton-pac.
Repo: github.com/tektoncd/operator
Latest: v0.80.0 (2026-06-09). LTS: v0.78.x (pipeline v1.6.x LTS, EOL 2026-12-08), v0.77.x (EOL 2026-08-21). Min K8s 1.28.
API group: operator.tekton.dev/v1alpha1
CR Model
| CR | Manages |
|---|---|
TektonConfig |
Top-level — installs/configures all components via profile |
TektonPipeline |
Pipeline component |
TektonTrigger |
Trigger component |
TektonDashboard |
Dashboard |
TektonChain |
Supply-chain security (SSDF/SLSA provenance) |
TektonResult |
Results API (pipeline run records) |
TektonPruner |
Event-based cleanup of old PipelineRuns/TaskRuns |
OpenShiftPipelinesAsCode |
Pipelines-as-Code (K8s since v0.80.0 via spec.platforms.kubernetes.pipelinesAsCode) |
TektonAddon |
Addons (OpenShift: templates, resolver tasks) |
TektonScheduler |
Multi-cluster scheduling (requires Kueue + cert-manager) |
Install TektonConfig, get everything. The user only needs to create TektonConfig with the desired profile — the operator creates the component CRs and manages their lifecycle. TektonResult and TektonChain are optional components NOT installed through TektonConfig currently.
Install
# 1. Operator itself (also installs pipelines/triggers/chains/dashboard via profile CRs below)
kubectl apply -f https://infra.tekton.dev/tekton-releases/operator/latest/release.yaml
# 2. Choose profile — installs the components
kubectl apply -f https://raw.githubusercontent.com/tektoncd/operator/main/config/crs/kubernetes/config/all/operator_v1alpha1_config_cr.yaml
Profiles
| Profile | Installs |
|---|---|
lite |
Pipeline |
basic |
Pipeline, Trigger, Chains |
all (K8s) |
Pipeline, Trigger, Chains, Dashboard |
all (OpenShift) |
Pipeline, Trigger, Chains, PaC, Addons |
Helm alternative
The operator repo ships charts/tekton-operator — install via Flux GitRepository pinned to a release tag (e.g. tekton-operator-0.79.0) + HelmRelease with installCRDs: true. The TektonConfig CR is created separately after install (post-install), and the operator reconciles it.
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.
- 9d ago First seen · 162 lines · 64 tokens per session scan A a88bcab7eeb0
tekton-operator is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 26d ago), licensed MIT. It adds 64 tokens to every session and 1,892 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-08-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.