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 tektongit 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)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/tekton"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton/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"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton.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.00049 | $0.00899 |
| Opus 5 | $0.00024 | $0.00449 |
| Sonnet 5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
tekton 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tekton — Skill Router
Operator: tektoncd/operator — latest v0.80.0 (2026-06-09); LTS v0.78.x (pipeline v1.6.x, EOL 2026-12-08), v0.77.x (EOL 2026-08-21). Min K8s 1.28.
Pipelines-as-Code: tektoncd/pipelines-as-code — latest v0.49.0 (2026-07-06).
API version: tekton.dev/v1 (authoring), operator.tekton.dev/v1alpha1 (operator CRs), pipelinesascode.tekton.dev/v1alpha1 (PaC Repository CR).
Overview
Tekton is Kubernetes-native CI/CD. Three surfaces:
- Authoring — writing PipelineRun/TaskRun YAML (resolvers, when/CEL, matrix, podTemplate, timeouts) in
tekton.dev/v1 - Operator — installs/manages Tekton components (Pipelines, Triggers, Dashboard, Chains, Results, PaC) via
TektonConfig+ component CRs - Pipelines-as-Code (PaC) — Git-native CI: PipelineRuns live in
.tekton/in the repo, triggered by Git events (push/PR/comment), results reported back as PR checks
Which Sub-Skill?
Match the user's request against the trigger keywords below, then call skill(name="<matched-skill>") to load the sub-skill's full content.
Routing Table
| Trigger keywords | User wants to... | Skill to load |
|---|---|---|
| pipelinerun, taskrun, resolver, git-resolver, taskRef, when, CEL, matrix, podTemplate, nodeSelector, tolerations, timeout, finally, workspaces, tekton.dev/v1 | Author/write Tekton pipeline YAML | tekton-pipelines |
| operator, TektonConfig, TektonPipeline, TektonTrigger, TektonDashboard, TektonChain, TektonResult, TektonPruner, profile, install tekton, upgrade tekton, component CR | Install/configure/manage Tekton components on a cluster | tekton-operator |
| pipelines-as-code, pipelinesascode, PaC, .tekton/, Repository CR, on-event, on-target-branch, on-path-change, on-comment, on-cel-expression, ChatOps, /retest, /test, tkn pac, git_auth_secret, trigger_comment | Git-native CI: pipelines in repo, triggered by Git events | tekton-pac |
Decision Tree
If routing is ambiguous:
- User is writing YAML for a pipeline (taskRef, when, matrix, podTemplate) →
tekton-pipelines - User is installing/configuring Tekton itself (TektonConfig CR, profiles, components) →
tekton-operator - User is setting up Git-triggered CI (Repository CR, .tekton annotations, webhooks, ChatOps) →
tekton-pac - Combination? → Load the one matching the primary action. Common pairs: operator installs Pipelines → PaC connects repos → pipelines authoring writes the runs. Authoring (
.tekton/files) + PaC (annotations on those files) are especially tight — load both for PaC work.
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 · 47 lines · 0 tokens per session scan A 72b90a6ce235
tekton is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 49 tokens to every session and 899 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-09-03.
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.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
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.