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 harness/harness-skills --skill create-infrastructuregit clone --depth 1 https://github.com/harness/harness-skillsWrote 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/harness/harness-skills/create-infrastructure)<a href="https://agentmods.dev/skills/harness/harness-skills/create-infrastructure"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/create-infrastructure.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01251 |
| Opus 5 | $0.00024 | $0.00626 |
| Sonnet 5 | $0.00010 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
create-infrastructure 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 8d 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:
- create-infrastructure — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Infrastructure
Generate Harness Infrastructure Definition YAML and push via MCP.
Instructions
- Identify infrastructure type - KubernetesDirect, KubernetesGcp (GKE), KubernetesAzure (AKS), ECS, or ServerlessAwsLambda
- Ensure prerequisites exist - The environment and cloud/cluster connector must be created first
- Generate YAML using the templates below, referencing the correct connector and environment
- Create via MCP using
harness_createwith resource_typeinfrastructure
Infrastructure Types
KubernetesDirect
infrastructureDefinition:
name: K8s Production
identifier: k8s_prod
orgIdentifier: default
projectIdentifier: my_project
environmentRef: prod
deploymentType: Kubernetes
type: KubernetesDirect
spec:
connectorRef: k8s_connector
namespace: my-app-prod
releaseName: release-<+INFRA_KEY_SHORT_ID>
allowSimultaneousDeployments: false
KubernetesGcp (GKE)
infrastructureDefinition:
name: GKE Cluster
identifier: gke_prod
environmentRef: prod
deploymentType: Kubernetes
type: KubernetesGcp
spec:
connectorRef: gcp_connector
cluster: my-gke-cluster
namespace: my-app
releaseName: release-<+INFRA_KEY_SHORT_ID>
KubernetesAzure (AKS)
infrastructureDefinition:
name: AKS Cluster
identifier: aks_prod
environmentRef: prod
deploymentType: Kubernetes
type: KubernetesAzure
spec:
connectorRef: azure_connector
subscriptionId: <subscription_id>
resourceGroup: my-rg
cluster: my-aks-cluster
namespace: my-app
releaseName: release-<+INFRA_KEY_SHORT_ID>
ECS
infrastructureDefinition:
name: ECS Fargate
identifier: ecs_prod
environmentRef: prod
deploymentType: ECS
type: ECS
spec:
connectorRef: aws_connector
region: us-east-1
cluster: my-ecs-cluster
ServerlessAwsLambda
infrastructureDefinition:
name: Lambda
identifier: lambda_prod
environmentRef: prod
deploymentType: ServerlessAwsLambda
type: ServerlessAwsLambda
spec:
connectorRef: aws_connector
region: us-east-1
stage: prod
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.
- 8d ago First seen · 190 lines · 49 tokens per session scan A 48a7400fd66c
create-infrastructure is a skill published in the GitHub repository harness/harness-skills (104 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,251 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.