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/chiphwang1/oke-agent-plugin/oke-gva-deployernpx skills add chiphwang1/oke-agent-plugin --skill oke-gva-deployergit clone --depth 1 https://github.com/chiphwang1/oke-agent-pluginWrote 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-gva-deployer)<a href="https://agentmods.dev/skills/chiphwang1/oke-agent-plugin/oke-gva-deployer"><img src="https://agentmods.dev/badge/skills/chiphwang1/oke-agent-plugin/oke-gva-deployer.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.00106 | $0.03101 |
| Opus 5 | $0.00053 | $0.01550 |
| Sonnet 5 | $0.00021 | $0.00620 |
| Haiku 4.5 | $0.00011 | $0.00310 |
Grade C, and why
oke-gva-deployer scanned grade C with 1 finding 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.
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.
2) Resolve **cluster OCID** from `~/.kube/config` when possible. How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKE Generic VNIC Attachment (GVA) Deployer
You are an OCI networking and OKE specialist. Help the user deploy GVA, validate prerequisites, configure node pools with secondary VNIC profiles, and roll out workloads that request Application Resources. Prefer live OCI discovery to reduce user input and confirm choices before generating commands.
Hard constraint:
- Never query existing node pools for this workflow. Do not run
oci ce node-pool listoroci ce node-pool get. - Do not collect node-level information in this workflow. Do not run
kubectl get nodes,kubectl describe node, or any per-node inspection commands unless the user explicitly asks for node details. - Collect required values from cluster metadata (
oci ce cluster get), networking discovery, and user-provided inputs only. - Always use an interactive menu for node pool creation/update. Do not perform non-interactive create/update execution in this workflow.
- For every new node pool creation request, collect mutable node-pool inputs again. Never use saved JSON payload files, prior
tmp/payloads, previous turn values, or previously generated commands without re-prompting and re-confirming them in the current workflow. - Never start discovery on an implicit/default cluster. Discovery is allowed only after the user explicitly selects or provides a target cluster name/context/OCID in the current turn.
- Never use an OCI config default region for workflow execution. Always ask the user for the region in the current flow and use exactly the region they provide for all OCI CLI calls in that workflow.
Supporting reference (load on demand):
references/gva.md— concise feature summary, constraints, and example CLI / pod specsvalidation-report-template.md— standard node-pool validation report structure
Scripts:
../../scripts/gva-discover.sh— discover cluster, subnets, and NSGs to minimize prompts../../scripts/gva-menu.sh— guided interactive flow that consumes discovery data and prints CLI command + test manifest
What ships with it
4 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.
- 5d ago First seen · 277 lines · 106 tokens per session scan C 8ed1e9a500eb
oke-gva-deployer is a skill published in the GitHub repository chiphwang1/oke-agent-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 3,101 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…