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-pacgit 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-pac)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/tekton-pac"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton-pac/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-pac"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/tekton-pac.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.00072 | $0.02701 |
| Opus 5 | $0.00036 | $0.01350 |
| Sonnet 5 | $0.00014 | $0.00540 |
| Haiku 4.5 | $0.00007 | $0.00270 |
Grade C, and why
tekton-pac 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 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.
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.
- **In-cluster git rewrite** — PaC mounts provider creds (`pac-gitauth-*`) bound to the EXTERNAL FQDN; pod→gateway→gitea hairpin 503s. Remap to internal service: `sed 's#^https://#http://#; s#@git.example.com#@gitea-http How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tekton-pac — Pipelines-as-Code
For authoring pipeline YAML see tekton-pipelines. For installing Tekton components see tekton-operator.
Repo: github.com/tektoncd/pipelines-as-code
Latest: v0.49.0 (2026-07-06). No official Helm chart — install via the vendored release.k8s.yaml release asset or the operator's OpenShiftPipelinesAsCode CR (K8s since operator v0.80.0).
API group: pipelinesascode.tekton.dev/v1alpha1
Model
Pipelines live in the repo (.tekton/ dir), versioned with your code. A Repository CR tells PaC which repo events to handle and where to run. PaC controller: receives webhook → matches event to Repository CR → fetches .tekton/ → resolves remote tasks (bundles each PipelineRun self-contained) → creates PipelineRuns → reports status back as PR checks/comments.
Providers: GitHub (App + Webhook), GitLab, Bitbucket Cloud/DC, Forgejo, Gitea.
Install
# Standalone (vendored release — pins exact version, no chart)
kubectl apply -f release.k8s.yaml # tektoncd/pipelines-as-code release asset
# Or via operator (v0.80.0+)
# TektonConfig spec.platforms.kubernetes.pipelinesAsCode.enable: true
Repository CR
One per git repo; created in the namespace where PipelineRuns run. Cannot be created in the PaC namespace itself.
apiVersion: pipelinesascode.tekton.dev/v1alpha1
kind: Repository
metadata:
name: my-repo
namespace: tekton-tasks
spec:
url: "https://git.example.com/org/my-repo"
git_provider:
type: "gitea" # gitea | forgejo | github | gitlab | bitbucket-cloud | bitbucket-datacenter
url: "http://gitea-http.gitea:3000" # provider API base
secret:
name: "gitea-webhook-config"
key: "provider.token"
webhook_secret:
name: "gitea-webhook-config"
key: "webhook.secret"
params: # optional custom params → {{ param }} / CEL variables
- name: docker_registry
value: "registry.example.com"
filter: pac.event_type == "pull_request"
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 · 205 lines · 72 tokens per session scan C a05e12878aa5
tekton-pac is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 26d ago), licensed MIT. It adds 72 tokens to every session and 2,701 once invoked, about $0.0004 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.