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 wangke19/gemini-ai-helpers --skill hcp-create-azuregit clone --depth 1 https://github.com/wangke19/gemini-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/wangke19/gemini-ai-helpers/hcp-create-azure)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/hcp-create-azure"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-azure/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/wangke19/gemini-ai-helpers/hcp-create-azure"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-azure.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00943 |
| Opus 5 | $0.00013 | $0.00472 |
| Sonnet 5 | $0.00005 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
HyperShift Azure 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 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.
This is a copy
94% identical to hcp-create-azure — 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperShift Azure Provider
This skill provides implementation guidance for creating HyperShift clusters on Azure, focusing on self-managed control plane configuration, resource group management, and Azure identity integration.
When to Use This Skill
This skill is automatically invoked by the /hcp:generate azure command to guide the Azure provider cluster creation process.
Prerequisites
- Azure CLI configured with appropriate credentials
- Azure subscription with sufficient quotas
- HyperShift operator installed and configured
- Pull secret for accessing OpenShift images
Azure Provider Overview
Azure Provider Peculiarities
- Self-managed control plane only: For ARO HCP use ARO CLI instead
- Resource groups: Auto-created during cluster creation
- Limited region availability: Not all Azure regions support all features
- Azure identity required: Service principal or managed identity configuration
- Virtual network integration: Requires proper VNet configuration
- Control plane runs on Azure VMs: Managed by HyperShift operator
Identity Configuration Options
Choose one of three identity methods:
- Managed + Data Plane Identities: Use
--managed-identities-fileAND--data-plane-identities-file - Workload Identities: Use
--workload-identities-file - OIDC Integration: Use
--oidc-issuer-url
Implementation Steps
Step 1: Parse Environment Requirements
Environment Detection:
- Development: "dev", "testing", "demo" → Standard_D4s_v3, SingleReplica
- Production: "prod", "enterprise" → Standard_D8s_v3+, HighlyAvailable
Step 2: Interactive Parameter Collection
Required Parameters:
-
Cluster Name & Location
🔹 **Cluster Name**: What would you like to name your cluster? 🔹 **Azure Location**: Which Azure region? [default: eastus] -
Identity Configuration Method
🔹 **Identity Method**: Choose Azure identity configuration: 1. Managed + Data Plane Identities (recommended) 2. Workload Identities 3. OIDC Integration
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 · 130 lines · 26 tokens per session scan A e7fb788f552c
HyperShift Azure 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 26 tokens to every session and 943 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-azure, 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".
openship-config
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
wrangler
Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, deployment, and Cloudflare resource management.
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.