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-pipelinesgit 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-pipelines)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/tekton-pipelines"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton-pipelines/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-pipelines"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton-pipelines.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.00052 | $0.01547 |
| Opus 5 | $0.00026 | $0.00773 |
| Sonnet 5 | $0.00010 | $0.00309 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade C, and why
tekton-pipelines scanned grade C with 1 finding 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 10d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
secretName: git-basic-auth-creds # Opaque secret with .gitconfig + .git-credentials keys How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tekton Pipelines — Authoring
For installing/configuring Tekton components see tekton-operator. For Git-native CI (pipelines in .tekton/) see tekton-pac.
Kubernetes-native CI/CD. Covers tekton.dev/v1 patterns.
When to Use
- Authoring PipelineRun / TaskRun YAML
- Configuring git/cluster/hub resolvers
- Setting nodeSelector/tolerations/affinity for CI pods
- Dynamic per-task node targeting via taskRunSpecs
- Matrix + param dynamic scheduling
- CEL when expressions
- Timeout hierarchy
- finally tasks
Not for: Tekton operator install/upgrade (see tekton-operator), Pipelines-as-Code / Git-triggered CI (see tekton-pac).
Core Patterns
Resolver-Based Task Refs
Prefer resolvers over embedded TaskSpecs:
tasks:
- name: build
taskRef:
resolver: git
params:
- name: url
value: https://github.com/org/repo
- name: revision
value: main
- name: pathInRepo
value: ci/tasks/build.yaml
Resolvers: git, cluster, hub. See TTL section below for cache config.
Git Authentication (Private Repos)
Authenticate against private Git repositories via the ServiceAccount's secrets — Tekton's creds-init init container reads kubernetes.io/basic-auth secrets automatically and configures git before any task step runs. No workspace plumbing needed.
# 1. Create the secret with annotation targeting the host
apiVersion: v1
kind: Secret
metadata:
name: git-creds
annotations:
tekton.dev/git-0: https://git.example.com # host-wide, any repo
type: kubernetes.io/basic-auth
stringData:
username: <user-or-bot-name>
password: <pat-or-token>
# 2. Attach to the PipelineRun's ServiceAccount
apiVersion: v1
kind: ServiceAccount
metadata:
name: default # or a dedicated pipeline SA
secrets:
- name: git-creds
For multiple hosts, increment the annotation index:
metadata:
annotations:
tekton.dev/git-0: https://github.com
tekton.dev/git-1: https://gitlab.com
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.
- 10d ago First seen · 241 lines · 52 tokens per session scan C 934070b8a220
tekton-pipelines is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 1,547 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). 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.