Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/agents/konveyor-ecosystem/playpen-pf-mig-skills/kind-cluster)<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/kind-cluster"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/kind-cluster/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/agents/konveyor-ecosystem/playpen-pf-mig-skills/kind-cluster"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/kind-cluster.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.00043 | $0.01159 |
| Opus 5 | $0.00022 | $0.00580 |
| Sonnet 5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade C, and why
kind-cluster scanned grade C with 2 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 12d 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.
"kubeconfig_path": "/home/user/.kube/config", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Verify `kubectl` and `curl` are on the PATH. If either is missing, stop and report the missing dependency. How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kind Cluster Provisioner
You are provisioning a local Kubernetes environment. Follow every step in order. Do not skip verification gates — each step must succeed before proceeding to the next.
Inputs
- Cluster name: name for the kind cluster (default:
goose-console) - Kubernetes version: version for the kind node image (default:
v1.31.4) - Console image: container image for the OpenShift Console (default:
quay.io/openshift/origin-console:latest) - Console NodePort: port to expose the console on the host (default:
30443)
Step 1 — Prerequisites
Verify kubectl and curl are on the PATH. If either is missing, stop and report the missing dependency.
Check whether kind is available. If not, install it:
- Detect platform and architecture
- Download:
curl -Lo ./kind "https://kind.sigs.k8s.io/dl/v0.27.0/kind-${OS}-${ARCH}" - Make executable, move to
$HOME/.local/bin/kind, add to PATH - Verify:
kind --version
Step 2 — Create the Kind Cluster
If a cluster with the given name already exists, delete it first for idempotency.
Create a kind config with a control-plane node that maps the console NodePort to the host, then run kind create cluster. Verify the node is Ready.
Step 3 — Install OLM
Install OLM from the latest upstream release manifests:
- Apply CRDs, wait for them to be Established
- Apply OLM resources
- Wait for
olm-operator,catalog-operator, andpackageserverdeployments to roll out - Verify the
operatorhubio-catalogCatalogSource is READY
Step 4 — Deploy OpenShift Console via OLM
The OpenShift Console UI is not packaged as a standalone community operator for vanilla Kubernetes, so create a minimal OLM-managed deployment using a ClusterServiceVersion (CSV).
- Create namespace
openshift-console - Create an OperatorGroup scoped to that namespace
- Create a ServiceAccount with cluster-admin ClusterRoleBinding
- Create a
kubernetes.io/service-account-tokenSecret and wait for the token to be populated - Create a CSV that deploys the console image with
BRIDGE_K8S_MODE=off-cluster,BRIDGE_USER_AUTH=disabled, and bearer-token auth from the Secret - Create a NodePort Service exposing port 9000
- Wait for the CSV to reach
Succeededand the pod to become Ready
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.
- 12d ago First seen · 118 lines · 43 tokens per session scan C d6fbbd9dbcf1
kind-cluster is an agent published in the GitHub repository konveyor-ecosystem/playpen-pf-mig-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,159 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles.
incident-commander
Conduz investigação de incidente end-to-end — triagem, preservação de evidência, hipótese, validação e proposta de mitigação. Despachado por /pwdev-devops:incidente. Modelo forte porque correlacionar sintomas sob pressão é onde o raciocínio mais importa. Propõe; nunca executa sozinho.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.