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-agent)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/hcp-create-agent"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-agent/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-agent"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-agent.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.00032 | $0.03392 |
| Opus 5 | $0.00016 | $0.01696 |
| Sonnet 5 | $0.00006 | $0.00678 |
| Haiku 4.5 | $0.00003 | $0.00339 |
Grade A, and why
HyperShift Agent 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 6d 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
98% identical to hcp-create-agent — 11 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 — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperShift Agent Provider
This skill provides implementation guidance for creating HyperShift clusters using the Agent provider, which is designed for bare metal and edge deployments where pre-provisioned agents are available.
When to Use This Skill
This skill is automatically invoked by the /hcp:generate agent command to guide the Agent provider cluster creation process.
Prerequisites
- HyperShift operator installed and configured
- Pre-provisioned agents available in a Kubernetes namespace
- Pull secret for accessing OpenShift images
- Understanding of the target deployment environment
Agent Provider Overview
What is the Agent Provider?
The Agent provider:
- Designed for bare metal and edge deployments
- Requires pre-provisioned agents (nodes registered in advance)
- No cloud provider automation - manual network configuration required
- Suitable for disconnected/airgapped environments
- Direct control over hardware and network configuration
Common Use Cases
- Edge Computing: Remote locations with limited connectivity
- Bare Metal: On-premises hardware without cloud automation
- Disconnected Environments: Airgapped environments with security requirements
- Custom Hardware: Specialized hardware configurations
- Regulatory Compliance: Environments requiring specific data locality
Implementation Steps
Step 1: Analyze Cluster Description
Parse the natural language description for Agent-specific requirements:
Environment Type Detection:
- Edge: "edge", "remote", "limited connectivity", "small footprint"
- Bare Metal: "bare metal", "on-premises", "physical hardware", "custom hardware"
- Disconnected: "airgapped", "disconnected", "offline", "secure environment"
Resource Indicators:
- Minimal: "small", "edge", "minimal resources", "single node"
- Standard: "production", "multi-node", "high availability"
Special Requirements:
- FIPS: "fips", "compliance", "security"
- Custom Storage: "local storage", "storage class", "persistent volumes"
- Network Isolation: "isolated", "private network", "custom networking"
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.
- 6d ago First seen · 509 lines · 32 tokens per session scan A a946bfc4f793
HyperShift Agent 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 32 tokens to every session and 3,392 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to hcp-create-agent, differing in 11 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".
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
vmware-vks
Use this skill whenever the user needs to manage vSphere Kubernetes Service (VKS) — Supervisor clusters, vSphere Namespaces, and TKC cluster lifecycle. Directly handles: check VKS compatibility, create/delete namespaces, create/scale/upgrade/delete TKC clusters, get kubeconfig, check Harbor registry. Always use this…
platform-build
Platform Developer: Stage 4 build task. Docker Compose setup, infra config, PR summary authoring, and Stage 4 gate writing for the platform workstream.
containerize
Build a minimal non-root OCI image for a uv-managed Python app with a pinned multi-stage Dockerfile, then scan, sign, and attest it. Use when containerizing Python.
trivy
Run Trivy scans for dependency vulnerabilities, IaC misconfigurations, secrets, licenses, SBOMs, and container images with the shared trivy.yaml. Use for any trivy command.