Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost.
$ npx skills add cbrock84/headcount --skill cloud-infrastructure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount cloud-infrastructure --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/technology/skills/cloud-infrastructure .claude/skills/cloud-infrastructure && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cloud-infrastructure" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/cloud-infrastructure into .claude/skills/cloud-infrastructure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-infrastructure", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/cloud-infrastructureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill cloud-infrastructure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount cloud-infrastructure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/technology/skills/cloud-infrastructure .agents/skills/cloud-infrastructure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cloud-infrastructure" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/cloud-infrastructure into .agents/skills/cloud-infrastructure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-infrastructure", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill cloud-infrastructure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount cloud-infrastructure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/technology/skills/cloud-infrastructure .cursor/skills/cloud-infrastructure && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cloud-infrastructure" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/cloud-infrastructure into .cursor/skills/cloud-infrastructure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-infrastructure", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/technology/skills/cloud-infrastructure--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill cloud-infrastructure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount cloud-infrastructure --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/technology/skills/cloud-infrastructure .gemini/skills/cloud-infrastructure && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cloud-infrastructure" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/cloud-infrastructure into .gemini/skills/cloud-infrastructure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-infrastructure", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount cloud-infrastructureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill cloud-infrastructure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/technology/skills/cloud-infrastructure .github/skills/cloud-infrastructure && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cloud-infrastructure" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/cloud-infrastructure into .github/skills/cloud-infrastructure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-infrastructure", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill cloud-infrastructure -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount cloud-infrastructure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/technology/skills/cloud-infrastructure .opencode/skills/cloud-infrastructure && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cloud-infrastructure" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/technology/skills/cloud-infrastructure into .opencode/skills/cloud-infrastructure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-infrastructure", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cloud-infrastructureDesigns and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost.
Cloud Infrastructure is an agent skill from cbrock84/headcount. Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in DevOps & Cloud, covering Infrastructure as code. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cloud Infrastructure loads about 1.1k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 584 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 584 words, ~1,061 tokens.
.claude/skills/cloud-infrastructure/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Cloud replaces capital cost with an operating cost that scales with carelessness. The discipline is mostly about making the environment reproducible and the spend visible.
Infrastructure created by hand cannot be reviewed, reproduced, or recovered. Define it as code, review it like code, and apply it through a pipeline rather than from a laptop.
The test: could you rebuild the environment from an empty account, and do you know that because you have done it? Untested reproducibility is a belief.
Console access for humans should be read-only in production by default. Write access exists for
emergencies, is time-bound, and is logged — see security:access-and-identity for the policy this
implements.
Separate environments by blast radius, not by name. Separate accounts or subscriptions give a hard boundary; separate namespaces in one account give a soft one that a misconfigured permission crosses.
Production data does not belong in lower environments. Where realistic data is needed, mask or synthesize it — a copied production database is a breach waiting for a misconfigured bucket, and it is one of the most common ways personal data escapes.
Default deny, then open what is needed. Public exposure should be a deliberate, reviewable act rather than the residue of a default.
Keep the trust boundary explicit and few: what is reachable from the internet, what is reachable between services, what reaches data stores. Most cloud incidents are not exotic — they are a storage bucket, a database, or a management interface that was reachable and should not have been.
Scale horizontally where you can and know your actual limits — the database connection ceiling, the third-party rate limit, the single-threaded component nobody remembers. Autoscaling in front of a hard downstream limit converts a slow system into an outage.
Design for the failure of a single instance and a single zone as routine. Region failure is a
business continuity decision with a real price attached, made with
operations:business-continuity-and-resilience rather than assumed by engineering.
Cost is an architectural property. Attribute spend by team and workload from the start; without tagging, cost becomes an unattributable aggregate that only ever gets addressed in a panic.
The usual large wins are unglamorous: idle non-production resources, over-provisioned instances, storage nobody deleted, and cross-zone data transfer nobody accounted for.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Platforms: AWS, Google Cloud, Microsoft Azure, and similar; managed application platforms — Fly.io, Render, Vercel, Railway — remove most of this work and are the right answer more often than engineering pride admits.
Orchestration where you need it: Kubernetes with a managed control plane, or a container service like ECS. Kubernetes is a platform team's worth of work; adopt it when you have the team.
Infrastructure as code and secrets: Terraform, OpenTofu, Pulumi, and similar, with secrets in a
managed store rather than in the state file. it-operations:cloud-administration covers the
corporate cloud estate, which is a different problem with overlapping tools.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in plugins/technology/skills/cloud-infrastructure of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Cloud Infrastructure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cloud Infrastructure this skillcbrock84/headcount | 2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 35k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Terraform Skillantonbabenko/terraform-skill | 2.4k | 1 repos | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Cloudflarehodgef/apiker | 127 | 7 repos | ~2.2k | Automated safety check: Pass | MIT |
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
antonbabenko/terraform-skill
A skill your agent uses when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift…
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
hodgef/apiker
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
cbrock84/headcount
Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.
Categories
Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Cloud Infrastructure is an agent skill from cbrock84/headcount. Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost.
Cloud Infrastructure fits situations like: tasks that involve Infrastructure as code.
Run `npx skills add cbrock84/headcount --skill cloud-infrastructure -a claude-code`. Or copy the skill folder (plugins/technology/skills/cloud-infrastructure in cbrock84/headcount) into .claude/skills/cloud-infrastructure in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cbrock84/headcount --skill cloud-infrastructure -a codex`. Or copy the skill folder (plugins/technology/skills/cloud-infrastructure in cbrock84/headcount) into .agents/skills/cloud-infrastructure in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill cloud-infrastructure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloud-infrastructure, .gemini/skills/cloud-infrastructure, .github/skills/cloud-infrastructure and .opencode/skills/cloud-infrastructure in your project.
SKILL.md names no scripts, command-line tools or credentials: Cloud Infrastructure is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Cloud Infrastructure is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 449 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Cloud Infrastructure: Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Terraform Skill (antonbabenko/terraform-skill, 2.4k stars), AWS Cdk Development (zxkane/aws-skills, 367 stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 259 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,001 GitHub stars. The repository holds 177 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.