Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/wangke19/gemini-ai-helpers/hcp-create-openstack)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/hcp-create-openstack"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-openstack.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.00028 | $0.00661 |
| Opus 5 | $0.00014 | $0.00331 |
| Sonnet 5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
HyperShift OpenStack Provider 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 4d 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.
This is a copy
94% identical to hcp-create-openstack — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperShift OpenStack Provider
This skill provides implementation guidance for creating HyperShift clusters on OpenStack, handling OpenStack-specific requirements including credentials, networking, and flavor selection.
When to Use This Skill
This skill is automatically invoked by the /hcp:generate openstack command to guide the OpenStack provider cluster creation process.
Prerequisites
- OpenStack CLI configured with appropriate credentials
- OpenStack project with sufficient quotas
- External network configured for floating IPs
- HyperShift operator installed and configured
OpenStack Provider Overview
OpenStack Provider Peculiarities
- Requires OpenStack credentials: Must have valid clouds.yaml or environment variables
- Floating IP networks needed: External network access for cluster API
- Flavor selection critical: Instance flavors affect performance and cost
- Custom images may be required: RHCOS images for worker nodes
- Network topology affects routing: Proper network configuration essential
Implementation Steps
Step 1: Interactive Parameter Collection
Required Parameters:
-
OpenStack Credentials
🔹 **OpenStack Credentials**: Path to OpenStack credentials file? - Usually clouds.yaml format - Example: /home/user/.config/openstack/clouds.yaml -
External Network
🔹 **External Network ID**: OpenStack external network UUID? - Required for floating IP allocation - Find with: openstack network list --external -
Flavor Selection
🔹 **Node Flavor**: Choose instance flavor: - m1.large (4 vCPU, 8GB RAM) - Standard workloads - m1.xlarge (8 vCPU, 16GB RAM) - Performance workloads - [default: m1.large]
Step 2: Generate Command
Standard Configuration:
hypershift create cluster openstack \
--name openstack-cluster \
--namespace openstack-cluster-ns \
--openstack-credentials-file /path/to/clouds.yaml \
--openstack-external-network-id <external-network-uuid> \
--openstack-node-flavor m1.large \
--base-domain example.com \
--pull-secret /path/to/pull-secret.json \
--release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi
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.
- 4d ago First seen · 99 lines · 28 tokens per session scan A 0085743202ad
HyperShift OpenStack Provider is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 661 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to hcp-create-openstack, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
azure-usage
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
setup
This skill should be used when user encounters "Azure MCP error", "Azure authentication failed", "az login required", "Azure CLI not found", or needs help configuring Azure MCP integration.
lov-deploy-to-vercel
A deployment workflow for publishing Vite, Next.js, Create React App, or static frontend projects on Vercel, a hosting service for web applications. It can also connect a custom domain and configure Cloudflare DNS records.
google-cloud-storage-diagnostic
Troubleshoots and diagnoses Google Cloud Storage (GCS) errors, permission denials, and access control issues. Use when a user encounters a 403 Permission Denied error on a Google Cloud bucket or object, or needs help diagnosing and resolving GCS IAM bindings, ACLs, UBLA, or service agent configurations.