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.
git 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/commands/openshift-eng/ai-helpers/generate)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/generate"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/generate.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.00014 | $0.02713 |
| Opus 5 | $0.00007 | $0.01357 |
| Sonnet 5 | $0.00003 | $0.00543 |
| Haiku 4.5 | $0.00001 | $0.00271 |
Grade A, and why
generate 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- generate — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
hcp:generate
Synopsis
/hcp:generate <provider> <cluster-description>
Description
The hcp:generate command translates natural language descriptions into precise, ready-to-execute hypershift create cluster commands. It supports multiple cloud providers and platforms, each with their specific requirements and best practices.
Important: This command generates commands for you to run - it does not provision clusters directly.
This command is particularly useful for:
- Generating complete, copy-paste-ready hypershift commands with proper parameters
- Applying provider-specific best practices and configurations automatically
- Handling complex parameter validation and smart defaults
- Providing interactive prompts for missing critical information
- Learning proper hypershift command syntax and options
Key Features
- Multi-Provider Support - AWS, Azure, KubeVirt, OpenStack, PowerVS, and Agent providers
- Smart Analysis - Extracts platform, configuration, and requirements from natural language
- Interactive Prompts - Asks for missing critical information with helpful guidance
- Provider Expertise - Applies platform-specific best practices and configurations
- Security Validation - Ensures safe parameter handling and credential management
- Namespace Management - Implements best practices for cluster isolation
Implementation
The hcp:generate command runs in multiple phases:
🎯 Phase 1: Load Provider-Specific Implementation Guidance
Invoke the appropriate skill based on provider using the Skill tool:
-
Provider:
aws→ Invokehcp-create-awsskill- Loads AWS-specific requirements and configurations
- Provides STS credentials handling
- Offers region and availability zone guidance
- Handles IAM roles and VPC configuration
-
Provider:
azure→ Invokehcp-create-azureskill- Loads Azure-specific requirements (self-managed control plane only)
- Provides resource group and location guidance
- Handles identity configuration options
- Manages virtual network 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.
- 4d ago First seen · 357 lines · 14 tokens per session scan A 91a1e873797c
generate is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,713 once invoked, about $0.0001 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 commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.