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 agentmods add skills/openshift-online/agent-control-plane/kindnpx skills add openshift-online/agent-control-plane --skill kindgit clone --depth 1 https://github.com/openshift-online/agent-control-planeWrote 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/openshift-online/agent-control-plane/kind)<a href="https://agentmods.dev/skills/openshift-online/agent-control-plane/kind"><img src="https://agentmods.dev/badge/skills/openshift-online/agent-control-plane/kind.svg" alt="Measured on agentmods" 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 | $0.00187 | $0.02644 |
| Opus 5 | $0.00093 | $0.01322 |
| Sonnet 5 | $0.00037 | $0.00529 |
| Haiku 4.5 | $0.00019 | $0.00264 |
Grade A, and why
kind 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 5d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kind Local Development Skill
Gateway mode (OPENSHELL_USE_GATEWAY=true) delegates sandbox lifecycle to an
OpenShell gateway via gRPC. The gateway runs per-tenant and manages Sandbox
CRs. Gateway resources (StatefulSet, certgen Job, TLS secrets) are deployed by
the control plane reconciler from the platform-config ConfigMap — no Helm
chart is involved.
Full Workflow: Cluster → Credential → Sandbox
Step 1 — Deploy the Kind Cluster (REQUIRED)
make kind-up OPENSHELL_USE_GATEWAY=true
Then in a separate terminal:
make kind-port-forward
Check ports with make kind-status.
Verify Tenant Namespaces
After kind-up completes, verify tenant namespaces exist and sandboxes can be created:
kubectl get ns tenant-a tenant-b
kubectl get pods -n tenant-a
Step 2 — Login with acpctl (REQUIRED)
The acpctl binary lives at components/ambient-cli/acpctl (prebuilt).
TOKEN=$(kubectl get secret test-user-token -n ambient-code \
-o jsonpath='{.data.token}' | base64 -d)
components/ambient-cli/acpctl login --url http://localhost:$API_PORT --token "$TOKEN"
Get $API_PORT from make kind-status (the "backend" port, typically 12856 on
the main branch).
Step 3 - Apply Tenant Fleet Definitions (REQUIRED)
The declarative approach uses acpctl apply -k to provision projects, agents,
providers, and credentials from kustomize overlays in examples/.
make kind-setup-vertex # configures Vertex AI env vars and K8s secrets
acpctl apply -k examples/overlays/tenant-a/
acpctl apply -k examples/overlays/tenant-b/
This creates:
- Projects (tenant-a, tenant-b)
- Agents with provider declarations (e.g.,
providers: ["vertex"]) - Providers (type:
vertex, referencing K8s secrets with OAuth2 refresh tokens) - K8s Secrets with Vertex AI credentials in each tenant namespace
Prerequisite:
make kind-setup-vertexmust run first to setANTHROPIC_VERTEX_PROJECT_ID,CLOUD_ML_REGION, and create K8s secrets with Vertex AI service account credentials in tenant namespaces.
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.
- 5d ago First seen · 273 lines · 187 tokens per session scan A 80419b53be15
kind is a skill published in the GitHub repository openshift-online/agent-control-plane (11 stars, last pushed 2d ago), licensed MIT. It adds 187 tokens to every session and 2,644 once invoked, about $0.0009 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
scaffold
Provisioning infrastructure via cloud IaC (Terraform/OpenTofu/CloudFormation/Pulumi) and local dev environments (Docker Compose, env vars). Use for IaC design or multi-cloud provisioning.
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.