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-aws)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/hcp-create-aws"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-aws/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-aws"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/hcp-create-aws.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.04347 |
| Opus 5 | $0.00016 | $0.02174 |
| Sonnet 5 | $0.00006 | $0.00869 |
| Haiku 4.5 | $0.00003 | $0.00435 |
Grade A, and why
HyperShift AWS 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
98% identical to hcp-create-aws — 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperShift AWS Provider
This skill provides implementation guidance for creating HyperShift clusters on AWS, handling AWS-specific requirements including STS credentials, IAM roles, VPC configuration, and regional best practices.
When to Use This Skill
This skill is automatically invoked by the /hcp:generate aws command to guide the AWS provider cluster creation process.
Prerequisites
- AWS CLI configured with appropriate credentials
- HyperShift operator installed and configured
- STS credentials file for the target AWS account
- IAM role with required permissions for HyperShift
- Pull secret for accessing OpenShift images
AWS Provider Overview
AWS Provider Peculiarities
- Requires AWS credentials (STS): Must have valid STS credentials file
- Region selection affects availability zones: Different regions have different AZ availability
- Instance types vary by region: Not all instance types available in all regions
- VPC CIDR must not conflict: Must not overlap with existing infrastructure
- IAM roles: Can be auto-created or use pre-existing roles
Common AWS Configurations
Development Environment:
- Single replica control plane (cost-effective)
- m5.large instances (balanced performance/cost)
- 2 availability zones (basic redundancy)
- Basic networking (public endpoints)
Production Environment:
- Highly available control plane
- m5.xlarge+ instances (better performance)
- 3+ availability zones (high availability)
- Custom VPC configuration
- KMS encryption enabled
Cost-Optimized Environment:
- Single NAT gateway
- Smaller instance types
- Minimal replicas
- Spot instances (where applicable)
Implementation Steps
Step 1: Analyze Cluster Description
Parse the natural language description for AWS-specific requirements:
Environment Type Detection:
- Development: "dev", "development", "testing", "demo", "sandbox"
- Production: "prod", "production", "critical", "enterprise"
- Cost-Optimized: "cheap", "cost", "minimal", "budget", "demo"
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 · 569 lines · 32 tokens per session scan A d5c022089e54
HyperShift AWS 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 4,347 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-aws, 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.
wrangler
Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, deployment, and Cloudflare resource management.
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
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.