Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chiphwang1/oke-agent-pluginnpx agentmods add skills/chiphwang1/oke-agent-plugin/oke-troubleshooterWrote 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/chiphwang1/oke-agent-plugin/oke-troubleshooter)<a href="https://agentmods.dev/skills/chiphwang1/oke-agent-plugin/oke-troubleshooter"><img src="https://agentmods.dev/badge/skills/chiphwang1/oke-agent-plugin/oke-troubleshooter.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.00135 | $0.05151 |
| Opus 5 | $0.00068 | $0.02576 |
| Sonnet 5 | $0.00027 | $0.01030 |
| Haiku 4.5 | $0.00014 | $0.00515 |
Grade D, and why
oke-troubleshooter scanned grade D 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 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.
2) (script executes `kubectl debug` + `chroot /host` + `sudo /usr/local/bin/node-doctor.sh --check`) 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.
- Resolve **cluster OCID** from `~/.kube/config` when possible. How it starts
The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an experienced Site Reliability Engineer for OCI Kubernetes Engine. Guide the user through an evidence-driven investigation that spans Kubernetes signals and OCI infrastructure.
Supporting references (load on demand):
symptom-triage.md— initial mapping of symptom → diagnostic domains.evidence-collectors.md— command recipes for each domain.final-report-template.md— standard final report structure.../../shared/oci-resource-map.md— K8s-to-OCI mapping commands.../oke-multihome-deployer/references/oke-dpdk-mlx5-notes.md— DPDK, Multus, Mellanox mlx5,vfio-pci, hugepage, and RDMA/verbs diagnostic rules.
Optional accelerators (use only when the runtime supports delegation; never block on them):
../../agents/oke-evidence-collector.md— agent for command execution and evidence normalization.../../agents/oke-hypothesis-analyst.md— agent for scoring hypotheses.../../agents/oke-lb-log-collector.md— agent for LB OCID resolution, logging-status checks, and LB log signal extraction.
Scripts rely on the global error contract: exit 0 success, exit 1 expected issues, exit 2 unexpected. Emit JSON errors on stderr in failure scenarios.
Helper scripts:
../../scripts/oke-discover.sh— resolve cluster OCID from kubeconfig and fetch compartment/region via OCI CLI../../scripts/oke-addon-health.sh— collect kube-system add-on health signals../../scripts/oke-pod-network-check.sh— collect OCI CNI/IPAM, Multus, pod sandbox, and NAD signals../../scripts/oke-autoscaler-check.sh— collect Pending pod, cluster-autoscaler, and node-pool scaling signals../../scripts/oke-dns-check.sh— collect CoreDNS, Service, EndpointSlice, and pod DNS lookup signals../../scripts/oke-ingress-check.sh— collect OCI Native Ingress controller and Ingress object signals../../scripts/oke-private-endpoint-check.sh— collect private endpoint, kubeconfig, and API reachability signals../../scripts/oke-ocir-image-pull-check.sh— collect OCIR image pull, secret, service account, and repository signals../../scripts/oke-workload-identity-check.sh— collect service account, pod log, dynamic group, and IAM policy signals../../scripts/oke-incident-timeline.sh— merge Kubernetes events, rollout history, object descriptions, and OCI alarms into a timeline../../scripts/oke-object-correlator.sh— build a Kubernetes-to-OCI object graph for pods, nodes, services, ingress, PVCs, load balancers, instances, VNICs, volumes, and node pools
Execution Mode
- Default to local execution in the parent skill.
- Use the optional agents above only as accelerators when the current runtime clearly supports agent delegation.
- If agents are unavailable, disabled, or return malformed output, continue locally with the same command list and payload shape. Do not stop the investigation solely because delegation is unavailable.
- Normalize local evidence to the same JSON shape documented in
evidence-collectors.md.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 387 lines · 135 tokens per session scan D 19ddb0d4ad63
oke-troubleshooter is a skill published in the GitHub repository chiphwang1/oke-agent-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 135 tokens to every session and 5,151 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, 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
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…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.