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.
git clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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/commands/openshift-eng/ai-helpers/extract-kubeconfig)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/extract-kubeconfig"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/extract-kubeconfig.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.1 | $0.00011 | $0.04054 |
| Opus 5 | $0.00005 | $0.02027 |
| Sonnet 5 | $0.00002 | $0.00811 |
| Haiku 4.5 | $0.00001 | $0.00405 |
Grade D, and why
extract-kubeconfig scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 /tmp/<namespace>-kubeconfig.yaml 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.
**IMPORTANT**: Use a dedicated temporary kubeconfig file for all build cluster operations. This prevents modifying the user's current kubeconfig context in `~/.kube/config`, which could disrupt other processes (e.g., run Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://raw.githubusercontent.com/<owner>/<repo>/<branch>/ci-operator/jobs/<org>/<repo_dir>/<periodics_file>" \ Copies of this mod
1 near-identical copy found in the catalogue:
- extract-kubeconfig — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:extract-kubeconfig
Synopsis
/ci:extract-kubeconfig <pr-url>
Description
The ci:extract-kubeconfig command extracts the kubeconfig from a running rehearsal/CI job in a GitHub PR. It checks the job's step status to determine if the cluster is ready, then connects to the build cluster to extract the kubeconfig from the running pod.
The command accepts:
- PR URL (required): GitHub PR URL in the
openshift/releaserepository
What it does:
- Validates the PR URL and checks ownership
- Finds running (PENDING) jobs on the PR
- Determines the build cluster (via GCS for public jobs, or via job config in the repo for qe-private-deck jobs)
- Logs into the build cluster and finds the CI namespace
- Checks step status via pod statuses to verify the cluster is ready
- Extracts the kubeconfig (and nested kubeconfig for HyperShift) from the running pod
- Verifies cluster health and reports results
Key features:
- Supports both standard and HyperShift (nested kubeconfig) clusters
- Supports both public (
prow.ci.openshift.org) and private (qe-private-deck) jobs - Uses ci-op namespace prefix on kubeconfig filenames to support multiple concurrent extractions
- Warns if you're not the PR author (may lack namespace access)
- Recognizes
waitsteps as valid running states for extraction
Prerequisites
-
GitHub CLI (
gh)- Check if installed:
which gh - Must be authenticated:
gh auth status
- Check if installed:
-
OpenShift CLI (
oc)- Check if installed:
which oc - Used to login to build clusters and extract kubeconfig
- Check if installed:
-
Google Cloud Storage (
gsutil) (optional)- Check if installed:
which gsutil - No authentication needed (test-platform-results bucket is public)
- If not installed, the command falls back to finding the build cluster from the job config in the openshift/release repo
- Check if installed:
-
PR in openshift/release repository
- The command only supports PRs in the
openshift/releaserepository - You should be the PR author to have access to the CI namespace on the build cluster
- The command only supports PRs in the
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 · 328 lines · 11 tokens per session scan D b147377383c3
extract-kubeconfig is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11 tokens to every session and 4,054 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, 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-30.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.