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 skills add openshift-eng/ai-helpers --skill hcp-create-powervsgit 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/skills/openshift-eng/ai-helpers/hcp-create-powervs)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/hcp-create-powervs"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/hcp-create-powervs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/hcp-create-powervs"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/hcp-create-powervs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 82 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 100 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00030 | $0.00967 |
| Opus 5 | $0.00015 | $0.00483 |
| Sonnet 5 | $0.00006 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
hcp-create-powervs 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- HyperShift PowerVS Provider — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperShift PowerVS Provider
This skill provides implementation guidance for creating HyperShift clusters on IBM Cloud PowerVS, handling PowerVS-specific requirements including IBM Cloud API keys, processor types, and resource group management.
When to Use This Skill
This skill is automatically invoked by the /hcp:generate powervs command to guide the PowerVS provider cluster creation process.
Prerequisites
- IBM Cloud CLI configured with API key
- PowerVS service instance configured
- IBM Cloud resource group access
- HyperShift operator installed and configured
PowerVS Provider Overview
PowerVS Provider Peculiarities
- IBM Cloud specific: Requires IBM Cloud API key and resource group
- Different regions have different capabilities: Service availability varies by region
- Limited instance types: Fewer processor types compared to other clouds
- Network setup complex: Requires careful network planning
- Processor type selection: Shared, dedicated, or capped options
Implementation Steps
Step 1: Interactive Parameter Collection
Required Parameters:
-
IBM Cloud Authentication
🔹 **IBM Cloud API Key**: Configure IBM Cloud authentication - Set IBMCLOUD_API_KEY environment variable, OR - Provide IBMCLOUD_CREDENTIALS file path -
Resource Group
🔹 **Resource Group**: IBM Cloud resource group name? - Must exist in your IBM Cloud account - Example: default, hypershift-rg -
Region Configuration
🔹 **Region**: IBM Cloud region? [default: us-south] 🔹 **Zone**: Availability zone? [default: us-south] -
Processor Configuration
🔹 **Memory**: Memory allocation per instance? [default: 32GB] 🔹 **Processors**: Number of processors? [default: 0.5] 🔹 **Processor Type**: Processor type? - shared (default) - Shared processor pool - dedicated - Dedicated processors - capped - Capped shared processors
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.
- 7d ago First seen · 146 lines · 30 tokens per session scan A 6e2408e70166
hcp-create-powervs is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 967 once invoked, about $0.0002 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-09-03.
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-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…
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).
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…