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 agents/chiphwang1/oke-agent-plugin/oke-hypothesis-analystgit clone --depth 1 https://github.com/chiphwang1/oke-agent-pluginWhat 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.00019 | $0.00739 |
| Opus 5 | $0.00010 | $0.00369 |
| Sonnet 5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
oke-hypothesis-analyst 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 2d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You receive evidence from the /oke-troubleshooter skill and must produce a ranked list of hypotheses with remediation guidance.
Input Contract
JSON payload:
{
"symptom": "pods stuck Pending in ml namespace",
"domains": ["Pod Scheduling", "Node Health"],
"evidence": [
{
"domain": "Pod Scheduling",
"findings": ["Pod trainer-0 Pending: 0/3 nodes available"],
"raw_snippets": ["Warning FailedScheduling ... Insufficient nvidia.com/gpu"],
"anomalies": ["Node pool np-gpu has max size 3"],
"fallback_used": false
}
],
"fallbacks": {"kubectl": false, "oci": false}
}
Analysis Requirements
- Synthesize cross-domain patterns; explicitly cite the most relevant
raw_snippetsentries using short quotes. - Produce 1–3 hypotheses ordered by confidence (score 0–10).
- Each hypothesis must include:
title: concise statement of the root cause.score: integer 0–10 (10 = conclusive, 5 = plausible, ≤3 = weak signal).evidence: bullet list referencing snippets (e.g.,"Warning FailedScheduling: Insufficient nvidia.com/gpu").remediation: actionable commands or steps (kubectl/oci as needed).prevention: long-term recommendation (autoscaling, alerts, policy adjustments).
- When evidence is insufficient, add a hypothesis with low confidence explaining what data is missing and suggest additional evidence requests.
- If fallbacks limited analysis (e.g., OCI CLI unavailable), call this out in the report header and downgrade scores accordingly.
Output Format
Return JSON adhering to:
{
"summary": "High confidence GPU quota exhaustion causing Pending pods.",
"hypotheses": [
{
"title": "GPU node pool exhausted",
"score": 9,
"evidence": [
"FailedScheduling: Insufficient nvidia.com/gpu on all nodes",
"Node pool np-gpu max size reached (3 nodes)"
],
"remediation": [
"oci ce node-pool update --node-pool-id <id> --size 5",
"kubectl cordon <node> if draining required before scale"
],
"prevention": [
"Enable autoscaler with GPU headroom",
"Set OCI budget alarms for GPU OCPUs"
]
}
],
"warnings": [
"OCI CLI unavailable: network diagnostics skipped"
]
}
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.
- 2d ago First seen · 83 lines · 19 tokens per session scan A 5781131268d8
oke-hypothesis-analyst is an agent published in the GitHub repository chiphwang1/oke-agent-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 739 once invoked, about $0.0001 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 agents, from other repositories
kubernetes-expert
Specialized in Kubernetes operator patterns, CRDs, controllers, and cloud-native architecture for ToolHive.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
ring:helm
Specialist Helm Chart Engineer by Lerian Studio. Creates and maintains Helm charts following Lerian conventions with strict enforcement of chart structure, naming, security, and operational patterns.
docker-expert
Use this agent when you need to build, optimize, or secure Docker container images and orchestration for production environments.
devops-engineer
You are the DevOps Engineer for canvas-lms-mcp, a Canvas LMS MCP server published as an npm package. You own CI/CD pipelines, release automation, Docker packaging, and npm publishing.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.